Open-source tool · Developer experience + AI agents
teamroom
Claude Code in one worktree, Codex in another, Gemini CLI in a third. Nothing tells them they are changing the same file until the merge. teamroom does.
My role. I designed and built it. It grew out of a Codex hackathon project.
The question
Agents work fast and alone. A merge conflict is the first time they learn about each other. How do they find out before the edit, not after?
The decision
Share work that is not pushed yet: uncommitted edits, untracked files, plans that are not code. Before an agent edits a file someone else is changing, pause it once and say who and why. The agent decides. Nothing is blocked for good.
The build
One command, no server. Worktrees on one machine share a file inside .git. Git hooks report what changed, whether or not the model cooperates. Any MCP agent gets the same news through tool results. A small optional server puts teammates in the same room.
Find out at the edit, not at the merge.
TypeScript · Node.js · MCP · Git hooks · CLI