How to export, save, and share a Claude Code conversation

You finished a Claude Code session and now you need that conversation somewhere else. Maybe you want a record of the reasoning before a big refactor. Maybe a teammate asked “how did you fix that?” and you want to hand them the transcript instead of explaining it from memory.

Here’s every way to get a conversation out of Claude Code.

Table of contents

Export the current conversation

Inside any Claude Code session, type:

/export

That opens a dialog to copy to clipboard or save to a file. If you already know the filename:

/export auth-refactor-notes.md

Writes the full conversation as plain text directly to disk. No prompt, no dialog. I’ve started doing this at the end of any session where the reasoning matters more than the code — debugging sessions, architecture decisions, anything I might want to reference later.

The export is plain text only. No JSON, no structured format. It’s a transcript.

Copy just the last response

If you don’t need the whole conversation, just the last thing Claude said:

/copy

Copies Claude’s most recent response to your clipboard. If the response has code blocks, you get an interactive picker to grab individual blocks instead of the full response. You can also pass a number to go further back: /copy 2 grabs the second-to-last response.

Name your sessions

Quick detour: /rename auth-refactor gives your session a human-readable name. Do this before you need to find it later. I have hundreds of sessions called “explain this function” that are useless now. You can also name at launch with claude -n "payment-webhook-debug".

If you don’t need to export but want to resume a previous session, I covered that in detail in my conversation history post (claude --continue, claude --resume, the /resume picker, all of it).

Share a conversation with someone

No built-in sharing link. Your options:

• Export to a file with /export session.md and send it
• Use /remote-control to let someone control your session from claude.ai
• Copy the file directly from ~/.claude/projects/<project>/ (sessions are stored as .jsonl files per project)

For most cases, /export to a file and dropping it in Slack or a PR comment is the fastest path.

Quick reference

For a deeper look at where conversations are stored, how to search across all your sessions, and a custom /history command that works like git log for conversations, see my full conversation history post.