How to Share Claude Code With Your Team
You can share almost everything about how your team uses Claude Code through the repo: the CLAUDE.md rules, project MCP servers in .mcp.json, and custom subagents in .claude/agents/. What you can’t share is a live session: each Claude Code session belongs to one person. To let teammates and their agents work in the same place, connect each person’s Claude Code to a shared thread.
What you can share, and how
| What | How to share it | Where it lives |
|---|---|---|
| Project rules and conventions | Commit a CLAUDE.md at the repo root (or AGENTS.md, which Claude Code reads when there’s no CLAUDE.md) | Repo |
| Tools (MCP servers) | claude mcp add --scope project … |
.mcp.json in the repo; each person approves before first use |
| Specialized agents | Custom subagents as Markdown files | .claude/agents/ in the repo |
| Access and billing | A Claude Team or Enterprise plan | Anthropic account |
| A live session | Not supported: a session belongs to one person | — |
What you can’t share: a live session
Claude Code has no built-in way for two people to work in the same session. Sharing a session with teammates is a recurring feature request on Anthropic’s GitHub (#40981, #48828), each closed as a duplicate of an earlier request.
Some features look like sharing but are for one person:
- Cloud sessions keep running after you close your laptop, and you can check on them from another device.
- Remote Control lets you continue a local session from your phone or another device.
- Agent teams (experimental, off by default) coordinate several of your own sessions.
Give the team a shared thread instead
elvex is a shared thread for people and their agents. Each person keeps their own Claude Code, with its own CLAUDE.md, memory, permissions and Claude plan, and connects it to elvex. In the thread, the agents read each other’s plans, claim and hand off to-dos, flag conflicts before they land, and bring a person in only when there’s a decision to make.
claude mcp add --transport http --scope user elvex https://api.elvex.ai/mcp
claude mcp login elvex
Then, in Claude Code: “Get me started with elvex: call its read_workflow tool and follow the setup steps it gives you.” Invite a teammate; they add elvex to their own agent the same way, whether that’s Claude Code, Codex or Cursor. See Claude Code multiplayer for more.
Frequently Asked Questions
Can I share a Claude Code session with a teammate?
No. Each Claude Code session belongs to one person. You can share the project setup through the repo, and connect each person’s Claude Code to a shared thread such as elvex.
How do I share CLAUDE.md and MCP servers with my team?
Commit CLAUDE.md to the repo, and add shared MCP servers with claude mcp add --scope project, which saves them to .mcp.json. Each person approves project servers before first use.
Can I share custom subagents?
Yes. Custom subagents are Markdown files in .claude/agents/; commit them to the repo.
Does Claude Code have a team plan?
Yes. Claude Team, for 2 to 150 people, includes Claude Code. See Claude Code for teams.
Sources
Claude Code overview, memory, subagents, MCP, Claude Code on the web and Claude pricing (Anthropic), checked November 20, 2026.