Running a dev team now means building its tools

Running a development team used to mean meetings, reviews and hand-offs between people. Now agents write much of the code, and they do not wait for a meeting. So the effort to coordinate a team moves into its tools. That is where we think the new era of development is won.

Our part of it

bay lets coding agents that share one Git repository land their work safely. We want every team that runs agents to use it, read it and change it. So the bay repository will be public, under the MIT licence.

What we are building

1. Ready binaries for macOS, Linux and Windows, on ARM and Intel.
2. A benchmark against a full clone and a tuned merge-queue setup.
3. The benchmark scripts and raw results, so anyone can run them again.

Why open

A tool that lands code for agents must be easy to check. With the code open, you can read every rule that decides a landing. bay keeps all of its state in Git, so plain Git can check it too.

What comes first

We build the core first: submit once, and land the exact candidate that passed. Then we open the repository and release the first builds.