KOMU records two main local log streams:
logs/audit.jsonllogs/sessions/<session-id>.jsonl
The audit log captures product-level actions such as:
- provider selection events
- plan generation
- review presentation
- execution approval or rejection
- execution results
- repair plan preparation
- profile changes
Audit records are JSONL entries so they remain easy to inspect and export.
Session logs capture a richer interactive trail:
- session start and end
- prompts
- generated plans
- review events
- execution results
- repair preparation
These logs are also used to reconstruct session summaries for komu sessions.
history.json stores durable task records for quick retrieval.
The audit and session logs remain the lower-level trace surface. Together they provide:
- operator-facing history
- machine-readable action traces
- explainability input
- future export potential
- logs are local only
- there is no remote log sink yet
- JSONL export exists by format rather than by a dedicated export command