How do I share a Claude Code session with my team?
Ways to share a Claude Code session with teammates: export the transcript, share a cloud session link, or hand over the work with branch, commit and a note.
It depends on what your teammate needs. To show them what happened, export the conversation with /export and send the file, or, for a cloud session, set its visibility to Team and send the link. To let them carry on the work, share the branch and a short handoff note rather than the session, because each person should run Claude Code under their own account. A local terminal session cannot be opened by someone else, and sharing a login breaks Anthropic's terms.
"Share the session" usually means one of three different things. Pick the one you actually need.
| What you want | Use | What the teammate gets |
|---|---|---|
| Show what the agent did and why | /export, or a shared cloud session link | A read-only record |
| Ask a teammate to review the result | A pull request | The diff, tests and your notes |
| Hand the task to a teammate | Branch, commit and a handoff note | Something their own session can continue |
Option 1: export the transcript#
In a terminal session, run:
/export session-notes.txtClaude Code writes the conversation as plain text to that file. Without a filename it opens a dialog to copy it to the clipboard or save it. Read it before you send it: transcripts can contain file contents, command output, internal URLs and, now and then, a token that was printed by mistake.
A transcript is a long read. For most teammates a five-line summary is more useful. Ask the session for one before you export:
Summarise this session for a teammate: what changed, what is still open, which files matter, and how to test it.Note that /share is not a sharing command in current versions of Claude Code. It is an alias for /bug, which sends feedback to Anthropic.
Option 2: share a cloud session link#
Sessions that run in Anthropic's cloud (Claude Code on the web, also used by Claude in Slack) can be shared by link. Change the session's visibility, then send the URL:
- Team and Enterprise accounts: visibility can be Private or Team. Team makes the session visible to members of your claude.ai organisation, and by default checks that the viewer has access to the GitHub repository.
- Pro and Max accounts: visibility can be Private or Public. Public means anyone signed in to claude.ai with the link. Repository access is not checked by default, so read the session first.
The viewer sees the latest state when they open the link; it does not update live. Anthropic's cloud sessions docs list the settings, including how to hide your name.
Local sessions have no share link. Remote Control lets you continue a local session from your phone or a browser, but it signs in as you, so it is not a way to hand the session to someone else.
Option 3: hand over the work, not the session#
When a teammate is going to continue the task, they need the state of the work, not your conversation. A good handoff has four parts:
- The branch, pushed.
- The last commit, so they start exactly where you stopped.
- What is done and what is next, in two or three lines each.
- Decisions made on the way ("prices are stored in cents"), so their session does not undo them.
Put it in the pull request description or the issue, then the teammate starts their own session on the branch:
git fetch && git switch feature-billing
claude "Read the handoff in PR #142 and continue from 'what is next'."Their session runs under their own plan, with their own permissions, and the decisions travel with the note. Rules every session should follow belong in the committed CLAUDE.md or AGENTS.md; Claude Code team collaboration covers which files to commit.
Why not share one account?#
It is tempting to sign two people into the same Claude account so they see the same sessions. Anthropic's terms do not allow sharing account credentials, and it mixes two people's usage, history and permissions. Team and Enterprise plans exist for organisations that want shared billing and admin. For a small team, one account each and a shared place for the work is simpler.
Where does Joxo fit?#
Joxo is a shared project for a team's coding agents. Each person's Claude Code (or Codex, Cursor, OpenCode and others) runs on their own computer and their own plan, and the sessions share one task board, decisions and a team chat. A handoff carries the branch, the commit and a note into the receiving agent's next turn, so nobody pastes it by hand. Teammates see what each agent has claimed and decided as it happens.
Read https://joxo.ai/skill.md and follow it to set up Joxo in this project.Handing a task from Claude Code to Codex shows a handoff between two different agents.
Frequently asked questions#
Can a teammate join my Claude Code session live?#
Not a local terminal session. Cloud sessions can be shared by link, but viewers see a snapshot, not a live view. To work at the same time, each person runs their own session on their own branch and they share decisions and handoffs.
Where are Claude Code transcripts stored?#
On your computer, under your user's .claude folder, one file per session. They are yours, not the team's. Use /export or a summary to share one.
Can my teammate resume my session with --resume?#
claude --resume lists sessions stored on that computer for that user, so a teammate on another computer will not see yours. Hand over the branch and a note instead.
Is it safe to share a transcript?#
Only after reading it. Transcripts can include secrets that were printed, private repository code and internal links. A short written summary is safer and more useful.