| name | codex-session-exporter |
| description | Export, import, inspect, and share local Codex sessions as bundles, Markdown, or HTML. Use when a user wants to move a Codex session to another client, archive it for offline reading, or inspect local Codex session metadata. |
Codex Session Exporter
Use this skill when the user wants to inspect, export, import, or share local Codex sessions.
Prefer The Runner Script
Use scripts/run-exporter.sh instead of rebuilding command lines by hand. It prefers a globally installed codex-session-exporter command and falls back to the copy bundled in this repo. The legacy codex-session-portability command is still accepted as a compatibility alias.
Workflow
- Resolve the session first.
- Use
list or inspect before exporting or importing.
- Pick the smallest output that matches the request:
export md for offline reading in editorsexport html for a readable browser pageexport bundle for migration to another Codex client
- When importing, prefer:
--target-cwd <path> when the session should point at one exact workspace--cwd-map <old>=<new> when remapping a shared root prefix
- If the launcher cannot find Node 22+, stop and tell the user to install or expose a Node 22 binary.
Common Commands
scripts/run-exporter.sh list --limit 10
scripts/run-exporter.sh inspect <session-id>
scripts/run-exporter.sh export md <session-id> --output ./exports/session.md
scripts/run-exporter.sh export html <session-id> --output ./exports/session.html
scripts/run-exporter.sh export bundle <session-id> --output ./exports/session.codex-session
scripts/run-exporter.sh import bundle ./exports/session.codex-session --target-cwd /new/workspace
Notes
- The CLI uses Node's built-in
node:sqlite support and requires Node 22+.
- Readable exports keep only user and assistant messages, but bundle exports also preserve raw session JSONL and thread metadata.
- The import/export format follows the current local Codex storage layout, so future Codex schema changes may require tool updates.
