Boxes.dev: Cloud development environment for AI coding agents to run and collabor

What it does

Boxes.dev provides cloud-based development environments designed specifically for AI coding agents like Codex and Claude Code. Each agent runs on its own dedicated Linux machine in the cloud rather than on a local computer or using git worktrees. Users can start agents from Slack, Linear, scheduled tasks, or API calls. The platform monitors and steers agents from desktop, mobile, or terminal interfaces. Idle machines automatically sleep to reduce costs.

Who it is for

The service targets developers and teams using AI coding agents like Codex or Claude Code as part of their workflow. It appeals to anyone frustrated with localhost development constraints, particularly teams running multiple agents in parallel on different tasks. Users need existing subscriptions to Codex or Claude Code to use the platform.

Pricing

The site does not show prices.

How it stands out

Boxes.dev positions itself as the first cloud-only agentic development environment. The core differentiator is isolation by default: each agent task gets a fresh, dedicated Linux machine with full filesystem access and no resource constraints. This contrasts with local worktrees, which require setup and share system resources. Sleeping devboxes are free, addressing cost concerns around parallel agent execution. The platform integrates deeply with existing workflows through Slack, Linear, scheduling, and API options. Dev environment migration is automated, and agents continue running when the user closes their laptop.

What a founder should check

A competitor should verify several things: First, whether the AI agent market is consolidating around specific models (Codex and Claude Code) or diversifying. If the models fragment, Boxes.dev's tight coupling to these two agents becomes a weakness. Second, understand switching costs for developers already using localhost workflows. The automatic environment migration is convenient, but teams with complex build systems may face hidden friction during porting. Third, examine the moat carefully. The cloud execution infrastructure itself is commodity compute, and the integration points (Slack, Linear, APIs) are standard. The real advantage appears to be the devbox snapshotting mechanism and cost structure around idle machines, but both could be replicated by larger cloud providers adding agent support to their existing dev environment products.

Thinking of building something like this?

Every launch here is a competitor to somebody's idea. If yours is close, check it against the market before you build: the Full Check names the rivals, the prices and the gaps.