The Git platform built for agents

Host, review and land code with agents on a Git platform that gives every change a Flight Path, built for the scale and throughput of agentic coding.

Get started
Works with any agent

One change, one Flight Path

See what the agent set out to do, what it did and why it can land.

Landing 42: search by dateExample
  1. Flight plan

    What the agent set out to do

  2. Takeoff

    Starts with what it needs to know

  3. Route

    What it read and changed

  4. Instruments

    Checked on every push

  5. Go-around

    Sent back, fixed, tried again

  6. Cleared to land

    Checks passed, approved

  7. Landed

    On main, in order

Instruments

  • Risk

    Low

    A small change

  • Slop

    Low

    Getting cleaner

  • Intent drift

    On course

    Matches the plan

Clearance

Landing 42

Checks

  • Tests
  • Code review
  • Security review

Approvals

1 of 1

In line

Landing 41 went first

Cleared to land

Black box: the full session is kept.

The problem

Git wasn’t built for a thousand writers

Agents push in parallel, start every session from scratch and produce more changes than any team can read. Plain Git makes them queue, retry and guess.

  • Agents overwriting each other on main

    Every commit lands on the server, in order, first try.

    Code as Transactions
  • More changes than people can review

    Review agents and required checks clear the routine, so people judge the rest.

    Review agents
  • Every session starting cold

    Each session opens with what the last ones did, decided and touched.

    Continuous Memory
  • Manually checking every agent change

    Every push runs checks on the exact commit before it can land.

    Continuous integration
  • Cloning everything to read three files

    Fetch only the files you open, or search the server without a clone.

    Fetch only what you need

A thousand agents can ship to main at the same moment, and every commit lands. No push races, no retry loops. The server lands each commit as a transaction, in order, so nobody’s work is overwritten.

Learn more about Code as Transactions

main log version 215

  1. v212writer-07src/retry.ts
  2. v213writer-31docs/limits.md
  3. v214writer-12src/backoff.ts
  4. v215writer-48test/retry.test.ts

Global from your first commit. YonedaRepo runs on a global network, with no region to choose and no mirrors to set up. Every account gets it, on every plan.

Learn more about Global by default

api.yonedarepo.com · one address, no region setting

Bring the Git you already use. Push and clone over HTTPS or SSH with LFS, organize repositories, forks and organizations, and drive it all from the yoneda CLI or MCP.

Learn more about Git hosting
$ git clone yoneda::https://api.yonedarepo.com/acme/app  demo
$ git commit -am "Retry on 503" && git push origin main
[main 9d1e0a7] Retry on 503
 1 file changed, 4 insertions(+), 1 deletion(-)
To yoneda::https://api.yonedarepo.com/acme/app
   4be81c2..9d1e0a7  main -> main

Clones that start small and stay that way. A yoneda clone brings commits and trees right away, and each file arrives the first time Git needs it. Want everything up front? Add --full.

Learn more about Fetch only what you need

demo main · commits and trees

  • src/retry.ts loaded
  • docs/limits.md on first read
  • assets/demo.mp4 on first read

Nothing reaches main until it has earned it. Review a Landing line by line, collect approvals on its latest commit, and land the moment every required gate passes.

Learn more about Landings & clearance

#12 Retry on 503 retry → main

  • 1 of 1 approval
  • check test passed
  • model check security passed

Cleared to land

Every push gets tested. Your checks run in a fresh container on the exact commit, and required checks hold the landing until they pass. Model checks grade a diff against your own rubric.

Learn more about Continuous integration

check test required on main

  • 9d1e0a7 Add retry helper passed
  • 2c5f9e1 Document backoff limits passed
  • 4be81c2 Tune retry limits running

Reviewers that read every change, so your people read the ones that matter. Code review, Security review, Slop review and Intent drift leave line comments on the change and record a check you can require, billed per use from your credit.

Learn more about Review agents

#12 Retry on 503 retry → main

  • Security review · mediumsrc/retry.ts:22 logs the request’s auth header when a retry fails.
  • Slop review · lowsrc/retry.ts:40 leftover console.debug.
  • check code-review passed
  • check security-review medium

Agents that remember. Every commit keeps the session that wrote it: what it read and what it said. Each new session opens with yoneda context: what the last ones did, the open Landings and the rules. No cold starts, no repeated mistakes.

Learn more about Continuous Memory
  • Add retry helpersession 7f2c · 9d1e0a7 · 3 declared reads
  • Document backoff limitssession 41ab · 2c5f9e1 · 2 declared reads
  • Transcript: 38 turns, 1 redacted
$ yoneda context
# YonedaRepo context for this clone
main at 4be81c2 (log version 215).

## Landing rules
- approvals required: 1; required checks: test
…
## Open change requests
- #12 Retry on 503 [branch retry at 9d1e0a7, by jane]

Answers without a clone. Search, blame and history on the server, at any version.

Learn more about Code search
  • src/retry.ts:14export function backoff(attempt: number)
  • docs/limits.md:3Backoff doubles up to 30 seconds.

One branch. A thousand writers. No retries. Plain Git makes concurrent writers take turns. YonedaRepo lands them all on the server.

1,000 writers commit to one branch at the same moment. How many land first time?
YonedaRepo
1,000 of 1,000
Plain Git
1 of 1,000

Plain Git takes the one push that arrives first and rejects the rest as non-fast-forward, so 999 writers fetch, rebase and push again. YonedaRepo merges every commit on the server.

  • Git’s own mergeMerges on the server match Git’s own three-way merge, so the result is the one you expect.
  • Every session on recordEach commit keeps the agent session that wrote it, and what that session read.
  • No new clientStock Git, the yoneda CLI or MCP. Agents and people use the same doors.

Give your agents a repository built for them.

Works with Git, our CLI and any MCP client.