Agent skill · daymade
read-codex-history
Reads, searches and exports local OpenAI Codex history without continuing work: session inventory, timelines, verbatim user input, indexed search, and rollout identity/fork lineage. Use when the user asks what they told Codex, wants a Session ID, or evidence of what a run did. Not for Claude Code (use read-claude-code-history); with no platform named, start at local-conversation-history.
What it needs
About 11k tokens when loaded.
What this skill does
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. Find a complete thread ID first For a pasted UUID prefix or an identity-only request, run this bounded lookup: Accept only exit 0 with status: unique and identityverified: true. The command queries matching state-index rows, includes archived/subagent entries, and verifies the unique candidate with the exact rollout locator. It does not export unrelated inventory, read conversation bodies, or probe writer locks. On ambiguity, show the returned candidates and ask for a longer prefix; on unavailable evidence, retain unknown. Return the verified ID and title, then stop. Load the rest of this Skill only for an additional requested result. Read lookup and JSON contracts only for exit handling, programmatic consumption or inventory JSON parsing. Codex 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 archivedsessions/ Full user/assistant/tool/compaction/fork event stream Exact-session evidence and keyword verification after indexed or physical preselection <codex-home>/logs.sqlite (pick the latest by mtime) Runtime events: per-event ts, level, target, feedbacklogbody, processuuid (embeds the OS pid), optional threadid Which live process is failing and how — error-shape bucketing and time distribution 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 sessionmeta.id matches. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills daymade/read-codex-history