What problem would this solve?
Memory files already persist a record per run (memory.ts formatRecord, timestamp, outcome, iterations, cost), but there's no command to browse run history. Users have to open the raw Markdown.
Proposed solution
Add loopflow logs [name] that reads .loopflow/memory/*.md and prints a table of recent runs (timestamp, outcome, iterations, cost). Optionally consider writing a small structured log alongside the Markdown so parsing is robust. This is a roadmap item.
Alternatives considered
No response
Scope
What problem would this solve?
Memory files already persist a record per run (memory.ts formatRecord, timestamp, outcome, iterations, cost), but there's no command to browse run history. Users have to open the raw Markdown.
Proposed solution
Add loopflow logs [name] that reads .loopflow/memory/*.md and prints a table of recent runs (timestamp, outcome, iterations, cost). Optionally consider writing a small structured log alongside the Markdown so parsing is robust. This is a roadmap item.
Alternatives considered
No response
Scope