Tool · Conversations & archives

Codex Session Transcript Exporter

Export one chosen coding conversation as readable messages with a source-line ledger.

Repository: CinvanaAI/codex-session-transcript-exporter

Explore the repository ↗Try or inspect it ↓

Recorded synthetic example. Source with a complete offline example.

See the idea in action.

`output/demo` contains `transcript.md`, `events.jsonl` and `manifest.json`, including a source content hash and explicit export settings. Existing output is preserved.

Example input

The included synthetic session mixes readable messages with events the default export omits.

Captured result

{
  "schema_version": "codex-session-transcript.v1",
  "source_filename": "synthetic_session.jsonl",
  "source_sha256": "63ddbbb4685c9470cb98ea0109ec248a8ebb46cc66a089046d468bc583e7ba6c",
  "included_events": 3,
  "skipped_events": 2,
  "secret_shape_redactions": 0,
  "cutoff_reached": false,
  "policy": {
    "include_tools": false,
    "include_status": false,
    "redact_secret_shapes": true,
    "user_label": "User",
    "assistant_label": "Assistant",
    "cutoff_phrase_configured": false
  },
  "files": {
    "events": "events.jsonl",
    "transcript": "transcript.md"
  }
}

Try the example.

From the repository root, follow the dependency requirements in the README. This example uses supplied synthetic material.

python -m pip install -e .
codex-session-transcript-exporter examples/synthetic_session.jsonl output/demo

`output/demo` contains `transcript.md`, `events.jsonl` and `manifest.json`, including a source content hash and explicit export settings. Existing output is preserved.

Complete setup and instructions ↗

The interesting part.

Export policy is explicit and inspectable; provenance does not require embedding a private absolute source path.

Public continuation

Where it came from.

Operational transcript exporter from the historical workbench Codex_Index tooling.

Rebuilds export around minimized messages, generic labels and no images/raw payloads.

The historical purpose was chatroom migration; current direct import compatibility is not established.

Source ↗

Follow the family: Builder, Factory and the Python Foundry

Historical context companionAgent Chatroom Ledger
Understand why canonical message identity and alternative context views were useful. A documented historical purpose; current direct import/consumption compatibility is not established.
Source 1 ↗, Source 2 ↗