On Cloudflare Workers and Durable Objects
Idle repos cost nothing. When an agent is working, you're billed per task — in dollars, not tokens. Scope it to one repo, one action, one deadline. Revoke it the moment you want it back.
The problem
They push to your repos with credentials built for people — long-lived tokens, personal access keys, OAuth scopes far wider than the job needs. One leak, or one grant nobody ever tightened, and you've got a production incident. There's still no clean way to say this agent, this repo, this action, until Friday — and I can revoke it right now.
How it works
One scope, one repo, one expiry. Not a standing key: a capability the agent spends against a budget you set.
Clone and push with plain git; the world still speaks it. Jujutsu (jj) is first-class. So is our own model, built so agents and humans can share a repo without either pretending to be the other. Every change is journaled against the identity behind the capability.
Every task carries its own cost, in dollars. Idle repos don't burn inference. A 402 is a ceiling you set, not an invoice you didn't expect.
Nothing to review means nothing passes. EdgeRef won't fake a green check to look finished.
Why it's different
Every capability is verified at the edge against a public key. There's no token database to steal and no signing secret on the server. Branch protection and compare-and-swap stop concurrent agents from overwriting each other. Objects are encrypted at rest. The stack scales to zero on Cloudflare — and you keep the keys.
Private beta. Tell us what your fleet does and we'll reply within a day.