The role has changed

Agents write the code.You make the calls.

You say what to build and judge whether it's right. This is already happening — what most people lack is the infrastructure to run it.

$curl -fsSL reeve.run/install.sh | bash
Runs on your machine, with your API keys.Use Claude today, swap to Codex tomorrow. Pipeline stays the same.Agent crashes, Reeve picks up from the checkpoint.
Watching studio/web-app
[12:04] ● REV-42 "Add OAuth provider support"
[12:04] ⠋ REV-42 Running claude…
[12:07] ↗ REV-42 PR → studio/web-app#89
[12:08] ✖ REV-42 review failed
[12:08] ↻ REV-42 Retrying (1/2)
[12:10] ✔ REV-42 review passed
[12:11] ✔ REV-42 Done (merged)
The new loop

Reeve connects your issue tracker to your agent in the background. You write tickets — it isolates, dispatches, and delivers PRs. Recovers from crashes. Never touches your main branch.

Any SourceBring your own issue tracker
Any AgentToday's strongest, tomorrow's too
IsolatedEvery task runs in its own environment
ReeveTakes the job, watches it, retries on failure
Your CallReeve delivers PRs, merging is yours
The bet

Between complex governance and pure execution, Reeve focuses on the latter.

While industry giants build comprehensive AI governance and knowledge graphs, Reeve focuses on the other end: providing a minimalist, isolated, and transparent execution container for agents. We don't try to stack intelligence in the orchestration layer; instead, through strict discipline, we let agent progress translate directly into productivity.

Agents get stronger every month. A thin layer lets progress pass through. A thick one becomes a ceiling.

42 seconds

A quick look at how Reeve runs the loop.