for agents: this page is markdown at https://switch-yard.dev/docs/introduction.md; every page is listed in llms.txt.
Introduction
Switchyard is a Git platform for teams whose code is written by many coding agents at once. Each agent works in its own task, a copy of the repository with a key that can push to that copy and nothing else. Switchyard merges every task live while the agents work, so it can warn them about overlaps early, and a merge queue merges each task on main once the project's checks pass and its rules let it merge, or a person approves it. GitHub stays where it is: a project can follow a GitHub repository, with GitHub holding main, and merge there.
What you get
- A task per agent. An agent starts a task, pushes to it with plain Git, the
yardCLI or MCP tools, and submits it when the work is done. Nothing an agent sends is ever lost: every push is stored before it is accepted. - Warnings while the work is going on. Two tasks that plan or change the same thing hear about it as it happens, with one suggestion each: stack on the other task, keep the change compatible, or stop because someone already builds it.
- Conflicts that never block. A conflict becomes an ordinary commit that records every side. Five steps try to fix it in order: Git's own merge, the file rules, the code rules, Claude, then a person. A fix a person makes once is remembered.
- A merge queue with proof. A task merges only after its checks pass on a test build of main with the tasks ahead of it. Every merge has a signed merge record naming what merged, who approved it and which checks passed.
- History you can undo. Every action is an entry in the project's history. Any entry can be undone, and the undo is itself an entry.
Who it is for
A team running Claude Code, Codex, Cursor or its own agents on one repository, from two agents to a fleet. It works with the Git you have and the GitHub you have. Reading the guarantees and the tradeoffs first tells you whether it fits today.
How to read these pages
- Start with the quickstart: install the CLI, sign in, connect a repository, start a task and watch it merge.
- How it works explains the system in its own words: concepts, guarantees, tradeoffs, limits and security.
- Guides take one job each, such as rules and checks and working as an agent.
- Reference pages are rendered from the product's own definitions, so they say what the software says: the REST API, the MCP tools, the CLI and the errors.
For agents
Every page here is plain Markdown at the same address with .md added, for example https://switch-yard.dev/docs/quickstart.md. llms.txt lists them all and llms-full.txt holds them in one file, so an agent told "read the Switchyard docs" can fetch exactly what a person reads.