getbay.io valid

bay

Run several coding agents in one codebase without stale branches, colliding merges or a broken main. Each agent submits its change once. bay checks the exact result, merges it into main and records why. It is free, MIT-licensed and runs on your machines.

For agents: Free MIT-licensed tool letting several coding agents share one Git repo; it checks each agent's change, merges to main and records why. Self-hosted, no runner n

coding agentsgit mergemulti-agentci checksopen sourcemit license

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-23T20:09:28.010Z. Cached copy · Source on getbay.io

# bay

> Run several coding agents in one codebase without stale branches, colliding merges or a broken main. Each agent submits its change once. bay checks the exact result, merges it into main and records why. It is free, MIT-licensed and runs on your machines.

Your agents finish in minutes. Why do they wait hours to merge? Stale branches, colliding merges and a broken main eat the time they saved. With bay, an agent submits once and moves on, and bay merges only what passed on the latest main. Free, open source, and your code stays on your machines.

## Names

- **main**: The one branch bay merges into, such as `main` or `dev`. You name it, and bay only adds to it.
- **merge**: One checked change added to main. `bay merge` submits one.
- **change**: One id for one intended outcome. The id stays when the agent revises the work.
- **view**: A sparse checkout of the paths that one change needs.
- **candidate**: The exact result that bay builds from the change and the latest main, then checks and merges.
- **check**: Any command that tests a candidate and returns a result.
- **evidence**: A record of what one check, review or runtime observation saw on one candidate, signed once you enrol keys.
- **runner**: The process that runs the checks on a candidate and merges it into main.

## Daily commands

- `bay start "fix the login page"` — open a view with only the paths this change needs
- `bay merge` — submit and return; a runner checks and merges it
- `bay status` — what each change does now, and why it waits
- `bay status --since` — what changed that affects my work
- `bay undo c7k2m4qa` — a new change that undoes one merge

## Free, open, private

bay is free for any team, of any size, under the MIT licence. There is no paid tier, no account and no sign-up. bay runs on your machines and talks only to your own Git remote. So it fits the most private repositories a company has.

- **Your code never leaves**: bay has no server, and it sends no telemetry. Your code goes only where your own Git remote is. Besides your remote, bay itself only downloads its releases from GitHub, at most once a day. You can turn that off.
- **Read every line**: bay is one Rust program with five direct dependencies, and it forbids unsafe code. A test counts every command, flag and reason code; a new one must take a step away from someone. Ask your coding agent to read the source before you trust it.
- **Checks run in a sandbox**: On macOS and Linux, a check sees only its candidate, its own files and system files. It gets no network unless your policy on main allows it.
- **Signed releases**: A hardware-held key signs every new release. The install script and `bay update` refuse a release that does not verify.
- **Build it anywhere**: Ready builds cover macOS and Linux, on ARM and Intel. The static Linux builds also run on ARM boards. Build it from source for Windows and other targets.
- **Build bay with us**: We build bay in the open. To join the work, email the founders
…

Related sites

Find similar publishers by meaning →

Other listed sites in AI agents and MCP. See the whole category →

Machine-readable: GET /v1/resolve?q=getbay.io · GET /v1/domain/getbay.io · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for getbay.io:
1. POST https://agentwebmap.com/v1/sites/getbay.io/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://getbay.io/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/getbay.io/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/getbay.io).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.