jeromeetienne / jeromeetienne/codespine

How to export a full Claude Code session transcript to a file

Open
#199 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

documentation
Dominant language
TypeScript
Stars
5
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Quick reference for dumping a long Claude Code terminal session to a file, verbatim and not as a summary.

Built-in command

/export session-dump.md

Writes the full conversation to session-dump.md in the current directory. Variants:

  • /export /Users/jetienne/webwork/codespine/session-dump.md — absolute path
  • /export session.txt — plain text instead of markdown
  • /export — no filename opens a menu (save to file or copy to clipboard)

The filename argument is optional. Include it to save straight to the file; omit it to get the menu.

Notes

  • Use /export, not /compact. /compact summarizes the conversation, which is the opposite of what we want here.
  • Do not prompt the model to "give me the whole conversation." The model only sees its context window and will paraphrase or summarize. /export reads from disk and is lossless.
  • /export operates on the currently active session. To export an older one, resume it first with claude --resume, pick it from the list, then run /export.

Most complete (raw) form

Every session is also saved as a JSONL file on disk:

~/.claude/projects/<encoded-project-path>/<session-id>.jsonl

For this repository the folder is:

/Users/jetienne/.claude/projects/-Users-jetienne-webwork-codespine/

The JSONL contains every message, tool call, and tool result (lossless, machine format). The largest file corresponds to the longest session.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No repository file is named. Start by locating the existing documentation or README section for Claude Code usage, then add the supplied /export examples and JSONL location. Done means readers can save the active transcript, resume an older session, and find the raw session file without relying on model-generated summaries.

Written by the indexing model from the issue text.

Assessment

Domain
cli, documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.