skills.rest
GaoSSR
GaoSSRCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

export

Export Codex session JSONL files into readable Markdown transcripts.

6|Updated Apr 24, 2026
Search Tags:#automation#transcript#markdown#codex#session#export
One-click install
npx skills add https://github.com/GaoSSR/codex-export-skill --skill export-gaossr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: export
Source: https://github.com/GaoSSR/codex-export-skill/tree/main/skills/export
Command: npx skills add https://github.com/GaoSSR/codex-export-skill --skill export-gaossr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Codex sessions are rich with context but hard to review or share. This Skill converts Codex conversation logs (JSONL) into clean, human-readable Markdown transcripts that are easy to read, archive, and feed into analyses or knowledge bases.

Core Features & Use Cases

  • One-command workflow: install and run with a simple command to export sessions.
  • Conversation-native usage: use within Codex via the $export trigger.
  • Markdown-first output: produces readable transcripts designed for review and long-term storage.
  • Flexible session selection: selects the active session or falls back to the most relevant recent session based on cwd or global recency.
  • Privacy-conscious defaults: redacts local paths and sensitive metadata by default.
  • Use Case: export current chats for post-hoc analysis, audit conversations, or generate knowledge artifacts like AGENTS.md.

Quick Start

In Codex, run the export command to save the current session as Markdown.

Frequently Asked Questions about export

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert Codex session JSONL files to Markdown transcripts?▼

You can convert Codex session JSONL files to Markdown transcripts by running the export command, which executes a Python exporter to generate readable Markdown outputs in a dedicated directory.

Can I export a specific Codex session by its session id or working directory?▼

Yes, you can export a specific Codex session by providing its session id or current working directory, with an automatic fallback to the most recent global session if no match is found.

Does the Codex session export redact sensitive local paths and metadata?▼

Yes, the Codex session exporter applies privacy-conscious defaults that automatically redact sensitive local paths and metadata when generating the readable Markdown transcripts.

What is the best way to archive Codex chat logs for post-hoc analysis?▼

The best way to archive Codex chat logs for post-hoc analysis is exporting them to Markdown transcripts, which are designed for easy review, long-term storage, and feeding into knowledge bases.

Where are the exported Markdown transcripts saved after converting a Codex session?▼

The exported Markdown transcripts are saved directly to the codex-session-exports directory within your active workspace after the Python exporter finishes processing the session.

Related Skills

Explore More Software Engineering Skills→
kevinslinkevinslin
21

dev.llm-session

Parse Codex session metadata from history JSONL and resume the matching session.

Community
Intermediate
Largo2z9Largo2z9
1

export-session

Export Claude Code sessions into structured markdown transcripts for archiving.

Community
Intermediate
cloudofgeorgecloudofgeorge

handoff

Summarize active conversations into handoff documents for other agents.

Community
Intermediate
codingSamsscodingSamss
11

orbit-session-diary

Convert Codex and Claude session JSONL logs into Markdown daily diary entries.

Community
Intermediate