Devboxes: branch previews your agents deploy.
Your agent wrote the feature. Now you want to click around it, not read a diff. A devbox runs the branch for real, at a URL you can open from any browser.
From "build me this" to a link you can click.
A devbox is a disposable machine that runs one GitHub repo's full stack: the app, its databases, its queues. Deploy a branch to it and the whole thing comes up really working, not mocked, behind a real URL.
Tell your agent what you want, in chat. It writes the code on a feature branch in your repo. OpenClaw, Hermes and Paperclip then deploy the branch to a devbox on their own, over MCP — create it, deploy, read logs, extend, tear down.
You open the preview link, click around the running app, and tell your agent what to change. Nothing merges until you have seen it work. Prefer to drive it yourself? Create a devbox and deploy any branch in one click from the dashboard.
Sokko works out how to run the repo.
No file needed. Around 16 stacks are detected automatically, among others:
When a repo comes up healthy, its working setup is saved for your org, and every later devbox for that repo starts from it — nobody solves the same repo twice. If a guess is wrong, your agent corrects it permanently in one deploy.
Public to your org, or not public at all.
The network choice is made when the devbox is created, and it is permanent for that devbox. One devbox is bound to one repo, permanently; siblings share the repo's secrets.
By default a devbox gets a public link on sokko.run. Visitors sign in first, and only members of your org get through; Sokko checks every visit. Send the link to a teammate and it just works — no tokens to pass around.
Want no public URL at all? Run the devbox in private mode. It is then reachable only inside your own Tailscale tailnet, and your tailnet's rules are the lock.
Disposable on purpose.
Devboxes are temporary by design — repo secrets outlive the devbox, so the next one picks up where it left off.
24 hours on the clock by default.
Stops after 4 idle hours. Data kept; the next deploy resumes it.
You or your agent extend it, up to 72 hours at a time.
The machine is reclaimed. Repo secrets are kept for the next one.
Flat price. No metered billing.
Devboxes are included in the flat plan price and run on their own machines, so a busy devbox never slows down your agents.
Questions
What is a devbox?
A disposable machine that runs one GitHub repo’s full stack (app, databases, queues), so you can test a branch in the browser at a real sokko.run URL. Agents deploy branches to it over MCP, and you can create and deploy one in a click from the dashboard.
Which agents can deploy to devboxes?
OpenClaw, Hermes and Paperclip drive devboxes over MCP: create one, deploy a branch, read logs, extend its life, tear it down. Cursor does not drive devboxes today. Your team can also deploy branches from the dashboard.
Does Cursor work with devboxes?
Not today. Cursor agents cannot create or deploy to devboxes over MCP. OpenClaw, Hermes and Paperclip can, and your team can deploy branches to a devbox from the dashboard.
Who can open a devbox preview link?
By default, visitors to your sokko.run link have to sign in, and only members of your org get through. Sokko checks every visit. If you want no public URL at all, run the devbox in private mode and reach it only inside your own Tailscale tailnet.
How long does a devbox live?
A devbox lives for 24 hours by default, and your agent can extend it up to 72 hours at a time. Idle devboxes stop after 4 hours and keep their data; the next deploy resumes them. When one expires, its repo secrets are kept for the next devbox on that repo.