[FEATURE] One-command session handoff from Claude Code CLI to a teammate
Status Open
Maintainer reply None cached
Workaround ✓ Mentioned in description ↑
Activity 3 comments · opened Oct 2, 2026
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
I often dig into a problem with Claude Code in the terminal, and then need to hand that context to a colleague.
claude.ai has a Share button, but the CLI has no equivalent. The only option is /export, which means manually passing a file around, and my teammate still can't continue the session in their own CLI. The usual workaround is asking Claude for a "handoff prompt", which loses detail.
Proposed Solution
- /share in the CLI creates a link scoped to my org (Team/Enterprise), optionally to specific people.
- The teammate runs claude --resume <link> (or /import <link>) and gets the full conversation context in their own environment and repo, as a fork of my session.
- Secrets are redacted automatically before sharing (env values, tokens, absolute paths), with a preview step. (?)
- Optional /share --summary sends a compact handoff summary instead of the full transcript. (?)
Alternative Solutions
_No response_
Priority
Medium - Would be very helpful
Feature Category
CLI commands and flags
Use Case Example
_No response_
Additional Context
_No response_
3 Comments
A workable version today: have Claude write a handoff file in the repo (what is done, what is next, each claim with a commit hash or file path), commit it, and your teammate starts a session with "read HANDOFF.md and confirm each commit exists before continuing." Handoffs go stale, so the check matters. Disclosure: I maintain Succession, a free MIT plugin that does this with /succession:close and /succession:seat; a script checks the cited commits and files. It is one seat per repo, and committing .succession/ for a team has caveats (see its README): https://github.com/thecontinuitylayer/succession
Disclosure: I'm Rob, and I built this.
Bellows does this now, for any agent rather than one. It's a desktop app (Windows, macOS, Linux) that runs Claude, Codex, Gemini CLI and any ACP agent, and its last release added Hand over.
Hand over turns a session into one
.bellows-sessionfile: the whole conversation with every tool call and result, plus a handover the agent writes when you hand over (where things stand, what's next, what to watch for). Keys and passwords are redacted before the file is written, and it carries a digest, so a file changed after it was made says so when it's opened.Your teammate opens it and sees who it's from, which agent, and how many prompts, replies and tool calls it holds. Then they pick their own checkout of the repo and carry on: their agent starts from your handover and the last exchanges, and the full conversation lands in their History. They don't even need the same agent. You worked in Claude, they can pick it up in Codex.
How it works: https://bellowsai.app/guides/hand-a-coding-agent-session-to-a-teammate?utm_source=github&utm_medium=reply
Give it a try, and tell me what would make it fit your team. We act fast on feedback.
Disclosure: I maintain claude-handoff (https://github.com/NeoAcar/claude-handoff), an unofficial open-source CLI that covers most of this today, minus the link.
What matches the proposal:
claude-handoff exportshows your sessions by title to pick from and writes the chosen one (transcript, subagent transcripts, persisted tool results) into.claude-shared/in the repo. After agit pull, the teammate runsclaude-handoff importand thenclaude --resume <id>in their own checkout, with the full history. Without a shared repo,export -owrites one file to send instead..envfiles and secret-named environment variables and removes those exact values wherever they appear, which catches secrets that have no recognisable pattern. It also scrubs something easy to miss: recent Claude Code versions record the signed-in account's email and organization UUID inside the transcript.export --dry-runshows what would be written, and a redaction log lists what was removed before yougit add.What it doesn't do: there is no share link and no org-level scoping (access is whoever can read the repo, or whoever you send the file to), no summary-only mode, and it's the same session travelling rather than a fork. Redaction lowers the risk rather than guaranteeing anything. Last verified end-to-end on Claude Code 2.1.289 on Linux.
npm i -g @neoacar/claude-handoff_Edited for 0.3.0: env-value scrubbing, session picker, single-file export._