Can several people use Claude Code on the same project?

Yes. Each person runs their own Claude Code session, and the sessions do not see each other. They share only what is in the repo, such as CLAUDE.md and the code. To share a plan and progress, connect every session to the same MCP server, such as Hamster, so they read the same tasks and write status back to one place.

How do I share context between Claude Code sessions?

Put the context somewhere every session can read. CLAUDE.md works for short, stable rules. For decisions and plans that change, run hamster sync to write the Briefs and Plans into .hamster/ in the repo, and connect the Hamster MCP server so a session can read the latest version and update it.

What is an MCP server in Claude Code?

MCP (Model Context Protocol) is how Claude Code calls tools outside the repo. An MCP server lists its tools, and Claude Code picks one when your request needs it. The Hamster MCP server at https://tryhamster.com/mcp gives Claude Code tools such as get_brief, get_next_task, and update_task_status, signed in through the browser with OAuth.

How do I connect Jira or Linear to Claude Code?

Connect Linear or Jira to Hamster once, at the team level, and turn on two-way sync. Hamster keeps its Briefs and Tasks in step with Linear projects and issues or Jira epics and issues, and Claude Code reaches them through the Hamster MCP server. Jira and Confluence may need to be enabled for your workspace first.

Does it work with my Claude Pro or Max subscription?

Yes. Hamster runs inside Claude Code as a plugin and an MCP server, so Claude Code keeps using the plan you already pay for. Hamster writes the Plan on its own models, so your Claude usage goes to building.

Does Hamster replace Claude Code?

No. Claude Code still writes the code and opens the pull request. Hamster holds what the team decided and the Plan that comes from it. Teammates on Cursor, Codex, and other MCP clients work from the same Plan.

Claude Code

Claude Code collaboration: give every teammate’s session the same plan

Claude Code has no shared workspace. Each session keeps its own context, and the only thing every teammate’s agent reads is what sits in the repo, like CLAUDE.md. To collaborate, connect every session to one MCP server that holds the plan, such as Hamster, so each agent reads the same tasks and writes its progress back.

With Hamster, your team agrees on a Brief and Hamster writes the Plan, which Claude Code reads and updates over MCP or from markdown synced into .hamster/.

Give every teammate’s Claude Code the same Plan.Free for 10 Briefs a month. No card needed.

Start free Start free

Claude Code asks Hamster for the next task on the team’s Plan.

What Claude Code shares today, and where it stops

Piece	What it shares	Where it stops
A session	Nothing. Its context stays with the person who opened it.	The next teammate starts from zero.
CLAUDE.md	Rules everyone’s agent reads, through git.	It drifts from what the team decided last week.
.mcp.json in the repo	The same MCP servers for every clone.	Tools, but no shared plan behind them.
Plugins and skills	The same commands for everyone.	Each person still plans alone.
Linear or Jira	The ticket.	The agent cannot read it without a connector.

Two engineers on the same feature end up with two plans. Whoever notices the overlap becomes the relay, pasting decisions from one chat into another.

The shared Plan, over MCP

The Hamster MCP server runs at https://tryhamster.com/mcp. Each call runs as the person who signed in, with their role, so there is no admin key to share. A team mostly uses the tools below.

Read the decision: get_briefget_plansearchThe Brief your team agreed on, and its Plan of tasks with acceptance criteria.
Take the next task: get_next_taskupdate_task_statusThe highest-priority task that nothing blocks, moved through todo, in_progress and done as the agent works.
Hand work on: update_taskcreate_subtasklink_pull_requestReassign, split, and attach the pull request to the Brief so the reviewer has it.
Ask the workspace: ask_hamsterget_hamster_replyQuestions about the team’s work, answered from the workspace and its connected tools. Hamster can also make the changes you ask for.

The full list, with the smaller tool set a cloud delivery job gets, is in MCP available tools.

The same Plan, as files in the repo

hamster sync writes Briefs, Tasks, Blueprints, and Methods into .hamster/ as markdown, and generates a project context skill that tells Claude Code where everything is. Add --watch and the files update as teammates change the Plan.

Claude Code runs `hamster sync` and lists the Briefs it pulled.

Files give the agent a fast read and MCP lets it write back, so most teams run both.

Linear, Jira, and Confluence stay in step

Connect them to Hamster once for the whole team. With two-way sync on, a Brief maps to a Linear project or Jira epic and each Task to an issue, so a status change in either place shows up in the other. Blueprints can mirror to Confluence pages. Claude Code needs no Atlassian connection of its own, because it reaches the work through the Hamster MCP server. See Linear, Jira, and Confluence.

Set it up in Claude Code

1. Install the Hamster plugin
```
/plugin marketplace add gethamster/plugin
/plugin install hamster@hamster-plugins
```
The plugin adds the hosted MCP server and the Ask and Ship skills. Run /reload-plugins after.
2. Run setup in your repo
```
/hamster:setup
```
It installs the CLI if needed, signs you in with hamster auth login, connects the repo with hamster init, and runs the first sync.
3. Take a task
Ask “what’s the next task on my Brief?” and Claude Code calls get_next_task. To work a whole Plan, run /hamster:ship with the Brief’s name; it asks before it pushes or opens a pull request.

No plugin? Add the server to .mcp.json in the repo so every clone gets it:

{
  "mcpServers": {
    "hamster": { "type": "http", "url": "https://tryhamster.com/mcp" }
  }
}

Teammates on Cursor or Codex install the same plugin and read the same Plan. Steps for each tool are in the plugin docs and MCP getting started.

Give your team’s Claude Code one Plan today

Start on your own and invite teammates when the first Brief is ready. It is free for 10 Briefs a month with the CLI and MCP included, and viewers are always free.

Questions people ask

Can several people use Claude Code on the same project?: Yes. Each person runs their own Claude Code session, and the sessions do not see each other. They share only what is in the repo, such as CLAUDE.md and the code. To share a plan and progress, connect every session to the same MCP server, such as Hamster, so they read the same tasks and write status back to one place.
How do I share context between Claude Code sessions?: Put the context somewhere every session can read. CLAUDE.md works for short, stable rules. For decisions and plans that change, run hamster sync to write the Briefs and Plans into .hamster/ in the repo, and connect the Hamster MCP server so a session can read the latest version and update it.
What is an MCP server in Claude Code?: MCP (Model Context Protocol) is how Claude Code calls tools outside the repo. An MCP server lists its tools, and Claude Code picks one when your request needs it. The Hamster MCP server at https://tryhamster.com/mcp gives Claude Code tools such as get_brief, get_next_task, and update_task_status, signed in through the browser with OAuth.
How do I connect Jira or Linear to Claude Code?: Connect Linear or Jira to Hamster once, at the team level, and turn on two-way sync. Hamster keeps its Briefs and Tasks in step with Linear projects and issues or Jira epics and issues, and Claude Code reaches them through the Hamster MCP server. Jira and Confluence may need to be enabled for your workspace first.
Does it work with my Claude Pro or Max subscription?: Yes. Hamster runs inside Claude Code as a plugin and an MCP server, so Claude Code keeps using the plan you already pay for. Hamster writes the Plan on its own models, so your Claude usage goes to building.
Does Hamster replace Claude Code?: No. Claude Code still writes the code and opens the pull request. Hamster holds what the team decided and the Plan that comes from it. Teammates on Cursor, Codex, and other MCP clients work from the same Plan.