Retro

Turn sessions into a ranked list of concrete improvements to the agent's environment, not the code. Read-only analysis; never modify the log files. Output a numbered proposal list with one verbatim (redacted) evidence line per finding, then let the user pick which to apply.

Scope. this, or a run straight after a build or a bug fix: the current session. Its conversation is already in context, so skip steps 1–3 and apply the lenses in step 4 to it. After the context was cleared, find that session's log in step 1 and mine only it. Otherwise: the N most recent sessions, steps 1–6.

Where the logs live

• Claude Code: ~/.claude/projects/<slug>/*.jsonl (top-level sessions). Per-session subagent transcripts are under <uuid>/subagents/agent-*.jsonl: skip these when counting "sessions"; they're part of a parent.
• Codex: ~/.codex/sessions/<year>/<month>/<day>/rollout-*.jsonl and rollout-*.jsonl.zst. Child-agent rollouts belong to their parent session.
• Grok: ~/.grok/sessions/<url-encoded cwd>/<id>/chat_history.jsonl. A cwd under /private/tmp is usually a headless panel run.
• agy (Antigravity CLI): every user prompt is in ~/.gemini/antigravity-cli/history.jsonl (display, workspace, conversationId); the rest of the conversation is ~/.gemini/antigravity-cli/conversations/<conversationId>.db, SQLite with protobuf payloads.

The first three are JSONL, one event per line. Stream .jsonl.zst through zstd -dc -- FILE; keep archives intact. If no Zstandard reader is available, report the excluded archives and the incomplete coverage. Open every log read-only.

1. Pick the N most recent sessions