Codex History Manager

Use codex-history-manager when the task is about local Codex history, not general ChatGPT or web chat history.

Codex stores local history in two places:

• - ~/.codex/state_5.sqlite for thread metadata
• INLINECODE2 and ~/.codex/archived_sessions/... for event logs

The bundled CLI is the source of truth for reading and mutating that state:

• - INLINECODE4

Default workflow

1. 1. For discovery, start with search.
2. For context, use show-thread or handoff.
3. For exports, use export-thread.
4. For cross-workspace reuse, prefer clone-thread over move-thread.
5. For writes, run a dry run first, then rerun with --apply.
6. For history body rewrites, always do plan-dangerous-edit, show the warning and change list to the user, get explicit approval in chat, then run apply-dangerous-edit.

Core commands

• - Search threads:

• - Read one thread:

• - Export transcript:

• - Create a handoff note:

• - Plan a dangerous history content rewrite:

• - Clone a thread into another workspace:

• - Move all threads in one workspace:

• - Clone all threads in one workspace:

• - Move a thread to another workspace:

• - Rebind provider metadata:

• - Rebind provider metadata for one workspace:

• - Rebind provider metadata for all local threads:

Safety rules

• - Never perform a write first. Use the default dry run or pass --dry-run.
• Only use --apply after reviewing the plan.
• Prefer cloning over moving unless the user explicitly wants to change ownership.
• Do not hand edit state_5.sqlite or rollout files if the CLI can do the job.
• If the user asks to modify message content, stop and confirm. You must first produce a dangerous edit plan, present the warning and change list in the conversation, and wait for explicit user approval before running apply-dangerous-edit.

Read these references only when needed:

• - Command details: references/commands.md
• Write safety and backups: references/safety.md
• Storage model: references/storage.md