read-codex-history
Installation
SKILL.md
Read Codex History
Read Codex evidence only. Do not continue the old task or change its project. If
the user wants execution after the read is complete, pass the verified evidence
to daymade-claude-code:continue-codex-work.
Codex has three different history surfaces
| Surface | Authority | Use |
|---|---|---|
<codex-home>/history.jsonl |
What the user submitted, keyed by Session ID and internal epoch timestamp | Exact recent user-input tables |
state_*.sqlite |
Inventory metadata such as cwd, title, update time, and rollout path | Fast listing and candidate discovery |
sessions/**/rollout-*.jsonl and archived_sessions/** |
Full user/assistant/tool/compaction/fork event stream | Session evidence, lineage, behavior audit, and keyword search |
Do not substitute one surface for another. A prompt-ledger row proves what was
submitted, not what the Agent answered. A state DB path is only a candidate until
the rollout's session_meta.id matches. A rollout can exist without a prompt-ledger
row, and a /fork prompt can exist without a child rollout.