Your agent transcript control room.
NetCodex turns Claude and Codex sessions into polished Markdown, Quarkdown and PDF-ready bundles without moving private transcripts into a SaaS account.
Sources
Claude + Codex
Storage
Temporary local jobs
Outputs
MD, QD, PDF bundle
Technical processor
Conversation export desk
Upload local transcript files, inspect the conversion path, and download clean artifacts from your machine. Supports JSONL, SQLite and ZIP bundles.
Ready for local files
No files analyzed
Pick local exports from Codex, Claude or a ZIP bundle.
- Upload
- Analyze
- Review
- Export
- Done
System activity
NetCodex is running locally. Your files stay on this machine during the export flow.
Drop a JSONL, SQLite or ZIP file to begin source detection.
Review the first rendered conversation.
Preview waits for an export.
Upload files, run Analyze if you want source confirmation, then Export to render the first conversation here.
From raw transcript to reviewable artifact.
Every export moves through the same disciplined path: identify the source, normalize the session, render the document, and package only what is meant to leave your machine.
$ netcodex analyze --source auto --json
-> detected_source: codex
$ netcodex export --source codex --formats md --json
-> step parse: success
$ netcodex export --source codex --formats md,qd,pdf --template galactic-guide --json
-> step render: success
$ netcodex export --local --source codex --formats md,qd,pdf
-> netcodex-manifest.json ready

Real files in. Clean documents out.
The visual system stays close to the actual work: local files, parsers, redaction and export artifacts.
Local privacy boundary
The browser talks to your local FastAPI runtime, and the MVP avoids accounts, history and cloud storage.
Agent-aware parsing
Codex rollout files and Claude JSONL sessions become one reviewable export model.
Documentation-grade output
Markdown preview, Quarkdown source and PDF fallback reporting are designed for real engineering notes.
Your conversations are already on disk.
Each tool keeps its chats in its own folder. Here is where, on Windows, macOS and Linux. Once installed, netcodex where lists the ones on your machine and the desk opens them for you.
| Tool | Status | Windows | macOS | Linux | What to import |
|---|---|---|---|---|---|
| Codex CLI / VS Code / DesktopCODEX_HOME | supported |
|
|
| rollout-*.jsonl, state_*.sqlite, session_index.jsonl |
| Claude Code CLI / VS CodeCLAUDE_CONFIG_DIR | supported |
|
|
| <session>.jsonl, <session>/subagents/agent-*.jsonl |
| Claude Desktop (Code tab)CLAUDE_CONFIG_DIR | supported |
|
|
| local_*.json (titles), <session>.jsonl (transcripts) |
| Claude Cowork | supported |
|
|
| local_<id>.json, local_<id>/.claude/projects/**/*.jsonl |
| Claude.ai (official data export)NETCODEX_CLAUDE_AI_EXPORT | supported |
|
|
| data-*.zip, conversations.json |
| GitHub Copilot Chat | supported |
|
|
| chatSessions/*.jsonl, chatSessions/*.json |
| GitHub Copilot CLI | supported |
|
|
| events.jsonl |
| Cline / Roo Code / Kilo Code | supported |
|
|
| api_conversation_history.json, ui_messages.json |
| Cursor | supported |
|
|
| state.vscdb |
| Gemini CLI | supported |
|
|
| session-*.json, logs.json |
| Continue | supported |
|
|
| <session>.json |
| AiderNETCODEX_AIDER_PATHS | supported |
|
|
| .aider.chat.history.md |
| Google Antigravity | best effort |
|
|
| conversation_summaries.db, conversations/*.db |
| Trae | encrypted, not supported |
|
|
| Encrypted: cannot be exported. |
| Windsurf | encrypted, not supported |
|
|
| Encrypted: cannot be exported. |
Built for people turning conversations into assets.
No invented customer logos. Just the roles this product has to serve: consultants, docs owners and platform teams handling sensitive agent work.
"This is the missing bridge between exploratory agent work and a client-safe document trail."
Independent consultant
"The preview-first flow makes it obvious what can be shared, edited and archived before a handoff."
Documentation lead
"A local API and clean fixture discipline are exactly the constraints that make this usable in serious teams."
Platform engineer
Start as a local tool. Scale as a workflow.
Pricing is intentionally visual for now. The product remains local-first while the workflow hardens.
- Manual uploads
- Markdown preview
- ZIP download
- No cloud history
- Batch-oriented workflow
- Quarkdown authoring path
- PDF fallback reports
- Parser priority roadmap
- Review checklists
- GitLab Flow alignment
- Security policy docs
- Shared export templates
Clear answers before you upload.
Privacy, supported sources, export formats and roadmap boundaries are spelled out before a transcript enters the workspace.
Open the local workspace and export your first conversation.
Start with one file, inspect the preview, and download a clean bundle when it is ready.