69 lines (48 loc) · 1.58 KB

History

Purpose

Phase 3 adds local task and session history so KOMU can feel like an operational product instead of a stateless command wrapper.

Task history

Task history entries store:

task text
summary
session ID
profile used
target labels
provider used
provider routing reason
plan source
risk level
execution outcome
repair summary if applicable
timestamps

The history service stores these entries in a structured JSON file under the KOMU data directory.

Session history

Session history is built from the existing session JSONL logs.

Phase 3 adds read access and session summaries so users can run:

komu sessions
komu sessions show <id>

Session summaries include:

entrypoint
start and end time
event count
task count
profiles involved
providers involved
recent event messages

Commands

komu history
komu history show <id>
komu sessions
komu sessions show <id>

The interactive shell also exposes history, history <id>, sessions, and session <id>.

Auditing and reviewability

History does not replace audit logs. Instead:

audit logs remain append-only event records
session logs remain detailed per-session traces
task history provides a readable operator-facing summary layer

This makes history useful for daily review without losing the lower-level trace data.

Limitations

history is local to the current machine
retention controls are not implemented yet
history does not yet aggregate across teams or shared workspaces
session summaries currently derive from local session events only