Boxes.dev is a cloud workbench designed for developers using coding agents like Claude Code and Codex. It belongs to the category of agent development environments but distinguishes itself by handing each agent a full Linux computer in the cloud. This product is for developers who want to scale their agent-driven workflows beyond a single laptop, enabling parallelism, persistence, and remote control. The core value is freeing coding agents from local constraints: instead of one agent at a time on your machine, you can launch many, each in its own isolated forked devbox, and manage them from any device. By migrating development environments to the cloud automatically, boxes.dev lets you focus on the work rather than the infrastructure.
The primary pain point boxes.dev solves is the limitation of running coding agents locally. When agents run on your laptop, they consume CPU, memory, and ports; you can only run one or a few at a time, and closing the lid kills the session. This forces developers to babysit agents or settle for sequential execution, slowing down experimentation and throughput. Boxes.dev removes these bottlenecks by giving every agent its own cloud VM that persists independently. This means you can spin up multiple agents tackling different tasks—like reworking authentication flows, auditing dependencies, and building integrations—all at once, without resource contention. The ability to leave agents running while you sleep or travel is a game-changer for complex, long-running coding tasks.
The first major feature group is "Full computers, not worktrees." Each fork is a real Linux box with its own filesystem, port forwarding to localhost, and your complete dev environment preinstalled. This is not just another git checkout; it is a fully functional machine that runs your app, services, and databases independently. The benefit is that agents can make changes to dependencies, edit the database schema, or break things without affecting other forks. Localhost port forwarding automatically follows the selected fork, so you can test changes in a browser or API client as if the agent were running on your machine. This isolation is crucial for correctness and parallel development.
The second feature group is "Isolation by default." Boxes.dev encourages spinning up a fresh cloud machine for every meaningful body of work. You can run as many agents as you want in parallel without configuring port numbers or managing resource limits. Each fork is created from a snapshot of your primary devbox, so every agent starts with your full dev environment already set up. Forks that go idle sleep automatically, consuming no usage. This design means you can fire off an agent for a quick bug fix, another for a new feature, and a third for a dependency update, all simultaneously, without stepping on each other's toes. The platform handles compute allocation and sleep cycles behind the scenes.
admin
The third feature group is "Desktop power, mobile control." Boxes.dev provides a desktop workbench on macOS (with iOS and Android apps) that centralizes agent management. From the workbench you can launch forks, inspect files and diffs, open terminals, manage ports, review changes, and commit. On mobile, you can kick off work, answer questions, approve requests, or open a terminal. There is no need for a separate "remote control" app; everything is native and cohesive. The workbench also includes thread lists with fork groups, live status, an integrated file viewer, diff mode, and persistent terminal sessions that survive disconnects. This omnichannel access means you can start a complex refactor from your desk, check progress from your phone on the go, and approve a merge from your tablet.
How boxes.dev works overall follows three steps. Step one: move your project into a cloud devbox. You pick a local folder, boxes.dev scans your environment and creates a setup plan for approval, then a coding agent recreates your dev environment in the cloud. This is automatic and encrypted. Step two: run each task on its own computer. Start Codex or Claude Code on a new machine; boxes.dev snapshots and forks the primary VM's filesystem, so no new setup is needed. Each agent gets full services, ports, and local database state. Step three: review, steer, and ship from anywhere. You read threads, browse diffs, answer questions, and approve agent requests. Manual testing is done via port forwarding to localhost, and you commit when ready. This workflow mirrors local development but scales horizontally.
Concrete use cases include reworking authentication flows, lowering API rate limits, fixing invoice PDF generation, and adding homepage buttons—all listed as examples on the site. Each task gets its own forked devbox where the agent runs the full app, can screenshot and test changes, and leaves reviewable work behind. Another use case is automated scheduling: set up weekly dependency audits via a trigger (e.g., every Monday at 6 AM) that runs Codex on a fresh fork and opens a PR when done. Slack and Linear integrations let you kick off threads from messaging or project management tools. The outcome is 10x faster development: build parallel agents, each with a full computer, and ship features without waiting.
Target users range from individual developers to engineering organizations. For solo developers on side projects, the Starter plan at $19/user/month includes 40 box-hours and up to 4 awake forks. The Pro plan at $99/user/month offers 250 box-hours and 10 awake forks for small teams. Teams plan has custom pricing with SSO, SCIM, RBAC, audit logs, and dedicated resources. Platforms supported include macOS 12+, iOS, Android, and CLI. Boxes.dev uses your existing Codex or Claude Code subscription—it does not sell tokens. The core takeaway is that boxes.dev is the only tool that hands every agent a real computer in the cloud and lets you steer it from any device, solving the parallel agent problem end-to-end.
Individual developers running coding agent workflows, side project builders, small teams of 2-5 developers collaborating on agent-driven tasks, and engineering teams deploying cloud coding agents across the organization. Also technical leads and platform engineers responsible for SSO, audit logs, spend controls, and security review.