See what the agent set out to do, what it did and why it can land.
Landing 42: search by dateExample
main
Flight plan
What the agent set out to do
Takeoff
Starts with what it needs to know
Route
What it read and changed
Instruments
Checked on every push
Go-around
Sent back, fixed, tried again
Cleared to land
Checks passed, approved
Landed
On main, in order
Instruments
Risk
Low
A small change
Slop
Low
Getting cleaner
Intent drift
On course
Matches the plan
Clearance
Landing 42L42
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.
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.
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.
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.
$ 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.
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.
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.
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.
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.
$ 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.
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.