boxctl
GitHub

Give Claude Code a computer of its own.

One command boots a fresh Firecracker microVM with your repo on it. Claude Code works there, its changes come back to you as branches, and the box is cleaned up when you're done. Your laptop stays yours.

curl -fsSL https://boxctl.io/get.sh | bash

macOS or Linux. Then boxctl login opens your browser to approve. Other install options

Work with it

cd your-project && boxctl claude

A fresh box gets a copy of your repo and you land in Claude Code, giving it tasks just as you would locally. When you exit, the work is waiting for you as box/* branches.

Hand it a task

boxctl claude --repo owner/name --goal "fix the flaky test"

With --repo and --goal there is no session to sit in: Claude works on its own, opens a pull request, and the box is cleaned up. Start it and get on with your day.

Why boxctl

A kernel of its own
Every box is a Firecracker microVM, not a container sharing your kernel. Claude can install, break and rebuild things without touching your machine.
Your laptop stays yours
The work happens on the box. Nothing runs against your files, your processes or your other credentials.
Only what the job needs
A box holds your repo and your GitHub and Claude logins, and nothing else of yours.
Changes come back as branches
When you exit, the work is waiting as box/* branches. Review it like any teammate's, merge what you like, drop the rest.
Hand it a task, walk away
With --repo and --goal, Claude works unattended and ends in a pull request. Start it and get on with your day.
Nothing left running
When the run ends the box is deleted. No idle VM to remember, no bill that keeps going.
Sessions survive a refresh
Open the same box in the browser dashboard: the terminal keeps its shell across reloads, and you can pop it out into its own window.
Show it to someone
Publish a port on a box at a public URL under boxctl.app, to try what Claude built without deploying it.
Open source, self-hostable
The CLI is open source, and boxctl can run next to your own boxctl-server if your code can't leave your infrastructure.

Every box is a real microVM with a kernel of its own, not a container sharing yours. While it runs it holds just what the job needs: your repo and your GitHub and Claude logins. Free plan: 50 box-hours a month, 2 boxes at a time. The CLI is open source.