teamroom shares file activity and plans across Claude Code, Codex, Cursor, Gemini CLI, and your teammates—even before changes are committed or pushed.
Local by default. No server required.
Codex is updating the theme. Claude Code is changing the header. Both need src/theme.ts. Worktrees keep their edits separate; teamroom surfaces the overlap.
Illustrative walkthrough · five stepsTheir files are isolated. Their tasks still overlap. Step through how a warning can help them adjust.
This example shows a possible response to a warning, not a guarantee of a clean merge. Claude Code and Gemini CLI hooks pause overlapping edits once. Other teamroom integrations rely on MCP checks; background warnings arrive on the next teamroom tool call.
Claude Code, Cursor, and Codex already offer native worktree workflows. Git worktrees work with any coding tool. Add teamroom when independent sessions need to know who else is changing the same files.
| Capability | Worktrees alone | With teamroom |
|---|---|---|
| Separate files for parallel agents | Yes | Provided by your worktrees |
| Shared view of uncommitted and untracked file activity | Not provided by isolation | Automatic reports |
| Plans visible before code exists | Not provided by isolation | Notes with expected file paths |
| File overlap warnings across independent tools | Not provided by isolation | Hooks and MCP checks |
| Teammates’ file activity before they push | Not provided by isolation | Optional shared server |
| Understand whether changes actually conflict | Git detects textual conflicts at merge | File overlap only; no merge simulation or semantic analysis |
Native platforms also offer coordination: Claude Code agent teams share tasks and messages, and Cursor Projects coordinate their agents. This table compares worktree isolation. teamroom adds awareness across independent tools and teammates. Sources checked September 28, 2026.
One agent, or clearly separate tasks? Worktrees may be enough. Use teamroom when overlapping work is hard to see until integration. Warnings are advisory: same-file edits can be compatible, and different-file changes can still conflict.
Git hooks and background reports share actual changes. Agents can add plans and ask about files before editing. Warning delivery depends on the integration.
Reports after Git events.
main, including uncommitted and untracked ones.Any agent, all session long.
teamroom_post_note announces a plan, teamroom_check_overlap asks before editing.Pauses an edit once in Claude Code and Gemini CLI.
Reports share what changed. Warnings give agents a chance to adjust.
By default the room is a file in your repo's .git directory, which every worktree shares. No server, no account, nothing leaves your machine. To include teammates on other machines, point the repo at a small shared server instead.
Three kinds of entries. Each one carries a session, a branch, the agent that sent it, and a list of file paths.
File contents are never shared. In local mode nothing leaves your machine at all. A shared server gets paths, branch names, commit ids and short messages; tokens are stored hashed there and kept in .git/teamroom.json on yours, readable only by you. Lockfiles are left out of overlap, and .teamroomignore leaves out more.
You need Node 22 or newer and git. No server, no account.
npm install --global teamroom
Hooks and agent configs launch teamroom by name, so it needs to be on your PATH.
teamroom init
Adds git hooks, MCP config for the agents it finds, an AGENTS.md block and hooks for the agents that support them. Commit what it wrote.
git worktree add ../app-header -b feat/header
cd ../app-header && codex # or claude, gemini, vibe
Each worktree is its own session. Worktrees you add later are set up automatically.
teamroom watch # every session, live
teamroom check src/theme.ts # who else is in this file
Use the dashboard or check a file yourself. Agents receive warnings through the hooks and MCP checks described above.
teamroom create --server https://teamroom.example.com
teamroom join '<invite link>' # on their machines
Needs a server your team can reach: teamroom serve, or the Docker image on Fly.io.