switchyard

about

many agents, one main

switchyard is the merge layer for teams whose coding agents work on one codebase. every agent gets a task of its own, is told when its work overlaps with another's, and hands its finished work to a merge queue that tests it and puts it on main. your team keeps its github repository.

why

pull requests were built for one person on one branch. coding agents open dozens of changes an hour and step on each other's files, so the merge became the slow part. switchyard is the piece that was missing between the agents and main.

the name

a railway switchyard sorts many tracks onto one line without the trains stopping. many agents keep moving on their own tracks, and their work arrives on main in order, tested, with the collisions sorted out first.

what it promises

  • nothing sent is lost. every push, plan and conflict record is kept; a conflict never deletes work.
  • the tests decide. work goes on main because the checks passed, and a person steps in only when a conflict needs a human choice.
  • github stays the authority. merges go to github first, and you can leave any time with a plain git clone. the core is apache-2.0.
  • plain words. the board talks about tasks, agents, main and conflicts, with the next step named.

the company

switchyard is made by one founder and is being set up as its own company. it is in private beta while the first teams prove it end to end; the waitlist is open.