Ask for the change.
Get a reviewed PR.
Tell Reeve what to build. It plans the work, waits for your approval, builds each task in an isolated container on your repo, and hands back a pull request with the tests to prove it.
GitHub · Isolated containers · Approval before spend
You
The signup form accepts emails with trailing spaces. Fix it and add a test.
Reeve
One task in acme/web: trim and validate the email in SignupForm, plus a regression test. Est. 40 credits. Approve?
You
Approve
Reeve
Done. PR #482 is open. The new test failed before the fix and passes now.
From a sentence to a merge-ready PR.
Ask
Describe the change in Reeve chat. A one-line fix or a whole feature.
Plan
Reeve sizes the work. Small asks become one task; bigger ones become a plan of tasks in dependency order, each checked against your actual code first.
Approve
Nothing runs and nothing is spent until you say go. You see the plan and the cost first.
Build
Each task runs in its own isolated container with a short-lived token scoped to your repo. Reeve reviews its own diff, then opens a pull request.
Prove
An independent check confirms it shipped: the PR exists and the tests that failed before pass now. Larger plans get one release review before merge.
An agent you can hand a repo to.
Your repo, your GitHub
Connect a repository through the Reeve GitHub App. Tokens are minted per task and expire. No shared keys, no personal access tokens.
Real pull requests
Work lands as a normal PR on your repo, reviewed and with tests, so your team can merge it the way it merges anything else.
You hold the merge
Approval gates sit before spend and before merge. Reeve never merges on its own.
Cost per task
Every run is metered and charged to credits, with a spend cap you set. You see what a change cost.
Watch it work
Follow every task from plan to PR in the pipeline tracker, or start one from there instead of chat.
Done means shipped
A task isn't marked done because the agent said so. It's done when the PR and test evidence back it up.
Talk to it where you work. Build where you trust.
Reeve in Slack
Coming next: @mention Reeve in the thread where the bug came up, approve the fix right there, and get the PR link back in the same thread.
See Reeve for Slackreeve.ci
The CI fleet our own agents ship through: GitHub Actions jobs on our own servers, so builds keep running when hosted runners don't. Early access.
Reserve early accessWe build Reeve with Reeve.
Reeve Code runs on our own repos every day. We're opening it to early teams now.