Guides
Guides for teams running AI coding agents
In shortThese guides cover the problems teams hit when several coding agents work in one codebase, and how to prevent them: why agents cause merge conflicts and broken builds, how to run several Claude Code sessions in one repository, how an MCP server can share team context, and how coordination compares with git worktrees.
Guides
| Guide | What it answers |
|---|---|
| AI coding agents and merge conflicts | Why teams of agents overwrite each other and break each other's code, and the five steps that prevent it |
| Multiple Claude Code sessions in one repository | A setup for parallel sessions, yours or your teammates', with worktrees and Lanes |
| An MCP server for team context | Which tools a team context server should offer, the rules it must follow, and how to add one |
| Lanes vs git worktrees | What isolation prevents, what it misses, and why teams use both |
By agent
Each supported agent has its own setup page: Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Kiro, Antigravity, Factory Droid, Qwen Code, opencode, Kilo Code and Amp. The agents overview compares them.