Codex Session Manager

Overview

Codex stores session transcripts as JSONL files under ~/.codex/sessions/YYYY/MM/DD/*.jsonl. Archived sessions may also exist under ~/.codex/archived_sessions/*.jsonl. Use the bundled manager to list candidates or export sessions into Markdown transcripts with a digest, timeline, message text, and linked tool-call details.

Default output folder: ~/.codex/session-markdown. Tell the user before exporting there, and mention any custom output folder they requested.

Quick Start

Let the user's wording choose the mode when it is clear; otherwise ask them to choose before exporting:

• Full mode: export all matching sessions. Use this for archive, backup, broad search, or "convert all sessions" requests.
• Specific mode: list candidate sessions first, ask the user to pick one, then export only that session.

Run from any directory:

python3 /path/to/codex-session-manager/scripts/manage_codex_sessions.py

Useful options:

• --mode full: export all matching sessions. This is the default.
• --mode specific --list-candidates: print a numbered candidate table and do not export.
• --mode specific --pick N: export the Nth candidate from the same filtered candidate list.
• --include-archived: also scan ~/.codex/archived_sessions.
• --project <text>: only export date/project keys containing this text.
• --session <text>: only export sessions whose id or filename contains this text.
• --since YYYY-MM-DD: only export sessions modified on or after this date.
• --limit N: export the N most recently modified matching sessions.
• --include-tool-details-inline: embed full tool payloads in the main session Markdown instead of sidecar files.

Specific Mode Candidate Flow

Use this flow when the user wants one Codex session, is unsure which session they need, or asks to inspect recent sessions before converting.

1. Run a candidate list command. Use --limit 20 by default unless the user asks for a different count.

python3 /path/to/codex-session-manager/scripts/manage_codex_sessions.py \
  --mode specific \
  --list-candidates \
  --limit 20

2. If the user gave a date, session id fragment, or archive hint, pass it through the same filters:

python3 /path/to/codex-session-manager/scripts/manage_codex_sessions.py \
  --mode specific \
  --list-candidates \
  --since 2026-06-01 \
  --include-archived \
  --limit 20

3. Present the numbered candidate rows to the user. The candidate table includes modified time, date/project key, short session id, cwd, and first user prompt excerpt.
4. After the user chooses a number, rerun with the exact same filters and --pick N.

If the user already gives an exact session id or unique fragment, use --mode specific --session <id-or-fragment> --list-candidates first when there is any ambiguity. Export with --pick 1 only when the candidate list has exactly one match.

Output Layout

The exporter writes:

~/.codex/session-markdown/
├── index.md
└── <date-or-archive-key>/
    ├── index.md
    ├── <session-id>.md
    └── tool-details/
        └── <session-id>.tools.md

Each session Markdown includes:

• Digest: source path, key, session id, cwd, timestamps, event/message/tool counts, and first user prompt excerpt.
• Linked tool details file when tool calls or results exist.
• Timeline: session metadata, user/assistant/developer messages, reasoning summaries, tool calls, and tool outputs.
• Short tool summaries inline, with full JSON payloads in the sidecar file by default.

Workflow

1. Confirm the source folder. Default to ~/.codex/sessions; add --include-archived when the user asks about archived sessions.
2. Ask the user to choose full mode or specific mode if they did not already make the choice.
3. Confirm or announce the output folder. Default to ~/.codex/session-markdown.
4. For full mode, run the manager script with any needed filters.
5. For specific mode, list candidates, get the user's chosen number, then export with --pick.
6. Report the number of sessions exported, output index path, and any parse warnings.

Notes

• Treat transcript data as private. It can contain prompts, file contents, command output, secrets accidentally pasted into chat, and tool results.
• Do not delete or modify original .jsonl files.
• Prefer sidecar tool details for large sessions. Inline tool payloads can make Markdown hard to search and load.