How does a team collaborate in Claude Code?

A team collaborates in Claude Code by sharing the project's setup through Git and keeping each person's work on its own branch. Commit a CLAUDE.md (or an AGENTS.md it imports), a project .mcp.json and a .claude/settings.json, give every task its own worktree, and review through pull requests. That covers the rules every session should follow. What it does not cover is the live part: who is working on what today, and what a teammate's session just decided.

What should a team commit to the repository?#

Claude Code reads its setup from files, and the files that live in the repository reach every teammate who pulls. These are the ones worth committing:

Personal overrides belong in .claude/settings.local.json, which stays on one computer. Claude Code's settings docs set out which file wins when two disagree.

If some teammates use Codex, put the real rules in AGENTS.md and make CLAUDE.md one line that imports it:

@AGENTS.md

Both agents then read one source of truth. Setting up Claude Code for a team goes through each file in more detail.

How do we share MCP servers without sharing secrets?#

Add the server at project scope, which writes it to .mcp.json at the repository root:

claude mcp add --transport http notion --scope project https://mcp.notion.com/mcp

Commit the file. Each teammate approves the server the first time Claude Code starts in that folder, and signs in with their own account where the server asks for one. If a server needs a key, reference an environment variable in the config and let each person set it locally. A key in a committed file is a key you have published.

Remember the approval step when someone says a tool is missing: a project server that nobody approved does not load. claude mcp list shows it as pending.

How do we stop two people's sessions colliding?#

Give each task its own working copy. Claude Code can start in a fresh Git worktree on its own branch:

claude --worktree feature-auth

Or make the worktree yourself and start Claude Code inside it:

git worktree add ../app-auth -b feature-auth
cd ../app-auth && claude

Two sessions in two worktrees cannot overwrite each other's files. They can still write conflicting code, so agree on who owns which task before anyone starts. A shared list with names on it is enough at first: an issue tracker, a GitHub Project or a TASKS.md. Add one rule to CLAUDE.md: read the list before starting, and put your name on a task before touching code. Stopping agents from editing the same files covers the failure cases.

How should the team review Claude Code's work?#

The same way you review anyone's: a pull request, read by a person who did not write it. Ask the session to open a draft pull request with a short description of what changed, how it was tested and what is still open. Put the verify command in the description so the reviewer can run it. A second agent can review too, as long as a person still reads the result before merging. Reviewing pull requests from several agents has a checklist.

What does Anthropic offer for teams?#

Three different things, often confused:

• Team and Enterprise plans. A company buys seats, and each person signs in to Claude Code with their own seat. This is the shape for an organisation that wants central billing and admin controls.
• Claude Code agent teams. One person runs a lead session that starts and coordinates several other sessions. It is a way for one developer to split their own work, not a way for several people to share a project. How agent teams compare with Joxo sets out the difference.
• Claude in Slack. Mention @Claude in a channel with a coding task and it starts a Claude Code cloud session. The original version runs under each person's own Pro or Max account; Team and Enterprise workspaces use Claude Tag. Anthropic's Claude Code in Slack docs explain which version applies.

None of the three gives two people's local sessions a shared view of each other's work.

Where does this setup stop working?#

The committed files carry rules that stay true for weeks. A team also produces facts that change every hour, and Git is a slow way to move those:

• A decision one session makes ("the API returns cents, not dollars") reaches a teammate's session only after a commit, a push, a pull and a fresh start.
• Two sessions can read the same task list in the same minute and both pick the top item.
• When work moves from your session to a teammate's, the handoff note has to be pasted into their session by hand.
• When a teammate's session is waiting on a question, nobody knows unless they are at that computer.

Where does Joxo help?#

Joxo is a shared project for a team's coding agents. Each teammate pastes one line into their own Claude Code session (or Codex, Cursor, OpenCode and others):

Read https://joxo.ai/skill.md and follow it to set up Joxo in this project.

Then the sessions share one task board, where only one agent can hold a task and a second claim is refused and told who holds it. A decision one session publishes reaches every teammate's agent. A handoff carries the branch, the commit and a note into the receiving agent's next turn. People and their agents talk in one team chat, and the iPhone app (in TestFlight) shows when one of your agents is waiting on you. Each person keeps their own Claude plan. Keep the committed files; Joxo carries the part that changes during the day. Joxo with Claude Code shows what changes in a session, and your team inside Claude Code shows a day of it.

Frequently asked questions#

Can two people share one Claude Code session?#

Not as a shared login. Each person should sign in with their own account, because Anthropic's terms do not allow sharing account credentials. Two people can look at one screen, but the practical way to work together is one session each, on separate branches, with shared rules in the repository.

Should CLAUDE.md be committed to Git?#

Yes, for project rules everyone should follow. Keep personal preferences in your user-level file or in a local file that is not committed, so one person's habits do not become everyone's rules.

Do teammates need the same Claude plan?#

No. Each person signs in with whatever plan they have, or with a seat on the company's Team or Enterprise plan. The committed files work the same for all of them.

How do I see what a teammate's Claude Code session is doing?#

Without extra tools, through their pull requests and commits. With Joxo, their agent's claimed tasks, decisions and handoffs show up on the shared board and in the team chat as they happen.