Boxes.dev is a cloud dev environment for developers who run Codex and Claude Code as everyday collaborators. Instead of putting several agents in local worktrees on one laptop, Boxes.dev gives each agent thread its own cloud VM. The product calls those isolated machines forks: each one has its own filesystem, processes, services, port forwarding, and local database state.
The core workflow starts from a local project. A developer moves the project into a cloud devbox, lets Boxes.dev scan the local setup, reviews the proposed setup plan, and then runs agent tasks on forked cloud machines. Each task can get a fresh environment that already has the project working, so one agent can refactor authentication while another tests invoices or builds a Slack integration. Because the work runs in the cloud, agents can keep going after the laptop closes, and the developer can steer them from desktop, mobile, web, or the `dvb` CLI.
Boxes.dev is built for people who are already using Codex or Claude Code heavily. The site states that users bring their existing Codex and Claude Code subscriptions or API access; Boxes.dev is not bundling those agents as a replacement. It focuses on the missing infrastructure around them: isolated compute, persistent terminals, port forwarding, reviewable diffs, mobile approvals, and repeatable devbox setup.
Pricing is usage-oriented. The official site lists a free Trial with 10 box-hours, a Starter plan at $19 per user per month with 40 included box-hours and prepaid overage, a Pro plan at $99 per user per month with 250 included box-hours and priority support, and a custom Teams plan for controls such as SSO, SCIM, RBAC, audit logs, dedicated pools, and security review. A box-hour is defined as one 4 vCPU / 8 GiB devbox awake for one hour, and sleeping forks do not consume usage.
The product is most useful for solo developers and engineering teams that want to parallelize agent work without overloading local hardware or hand-managing ports, databases, and branches. The caveat is that it adds a cloud-workbench layer to the workflow. Teams should be comfortable with remote dev environments and should review the security model before moving sensitive repositories into any hosted workspace.
Boxes.dev also changes how teams review agent output. Instead of asking an agent to describe what changed, the developer can open the relevant fork, inspect files, browse diffs, test forwarded ports, and commit when ready. That makes it better suited to serious coding work than a simple chat wrapper, especially when several long-running tasks need to happen at the same time.