Overview

bay is the landing layer for agent fleets. It is a small open-source command for coding agents that share one Git repository. An agent opens a change, edits, and asks bay to land it. bay builds the candidate, checks that exact result, and lands it on trunk. An executor finishes the landing after the agent leaves. Your repository stays an ordinary Git repository on the host you already have.

Who bay is for

bay is for teams that run many coding agents against one Git repository. It suits a fleet where no person can watch each merge. bay is not a code-review tool. No model sits in its decision path.

The daily loop

Five commands make the daily loop. Each command prints one JSON result, and the agent reads it. A refusal names the reason, what you can still do, and when to retry.

bay start CARD-123 --paths src/api   # open a view of the paths this change needs
# ... the agent edits ...
bay land                             # check that exact result, then return
bay status                           # what each change does now, and why it waits
bay watch                            # what changed that affects my work
bay undo c7k2m4                      # a new change that undoes one landing

What bay promises

• What lands is exactly what bay checked.
• Unknown is never a pass.
• The agent can leave after bay land.
• A retry never lands twice.
• Every refusal says what to do next.
• Git stays the only store.

Read next

• Install: put bay on a machine and check it with bay doctor.
• Quickstart: land a first change.
• Concepts: the one meaning of each name.
• Agents and hooks: the bay skill and the agent products that bay supports.
• Executors: the process that finishes each landing.
• Configuration, Update, CLI reference, and Results and refusals: the details.