Boxes.dev: ditch localhost; run Claude Code and Codex in the cloud

Hi HN, we’re Nick and Drew, and we’re building boxes.dev – the first cloud-only agentic dev environment (ADE) that gives every Codex and Claude Code agent its own cloud computer.We’re two engineers who previously built Gem (co-founder/CTO and first hire), and we spent the last year coding almost exclusively using Codex and Claude Code. It’s been a huge change to how we code, and it’s been exhilarating seeing the models keep getting better – but we eventually realized that developing on localhost was holding us back:- Git worktrees are clunky to set up and use for parallelizing work - It’s 2026, but somehow everyone is still walking around with laptops cracked open or SSHing into mac minis in their garage so their agents don’t stop working. - Mobile is treated like an afterthought even though coding is just texting now We started hitting resource constraints when multiple parallel agents test their own work by running the full app locally. - We tried different products, but couldn’t find any that solved all of our pain points – so we pivoted and decided to just build the ADE we wanted for ourselves.Boxes.dev is a desktop and mobile app that lets you run Claude Code, Codex (using your subscription!), and the full dev environment for whatever you’re building, all on remote compute. It’s similar to Conductor or the Codex desktop app, except everything is in the cloud.We use coding agents to scan your local dev setup and port it to the cloud. Then every Claude Code/Codex thread starts from a snapshot of the full setup, with its own filesystem and compute. No more git worktrees, no more cracked-open laptops, and your coding agents can actually test their work end-to-end because they can run your full app in isolation.We’ve mirrored the Claude Code and Codex UX to feel natural to power users, and also have a fully-featured mobile app (no handoffs or remote control), plus scheduled automations and a Slack integration.We’re obviously biased, but we’ve been buildin

Hacker NewsToolAISource
0Sign in to voteCopy link

FL score

72

out of 100

Verdict

VALIDATE

high confidence

Competition

No competitor data yet

Trend

No signal yet

Cloud IDE that runs AI coding agents with full isolated environments instead of forcing them to work on localhost.

The pain

Developers using Claude Code and Codex hit hard walls: agents can't parallelize work without git worktree complexity, can't run full app tests in isolation, and developers are tethered to laptops or garage mac minis to keep agents running. Mobile coding is impossible. Resource constraints explode when multiple agents test simultaneously.

The gap

Existing tools (Conductor, Codex desktop app) either don't run in cloud or don't give agents isolated compute environments. No product lets an agent spin up its own cloud computer, run the full app, test it, and report back, all without touching localhost.

Build angle

The founders experienced the problem directly while building with agents for a year. They tried existing solutions and found nothing. They're building the specific tool they needed. The timing is right: Claude Code and Codex are becoming primary dev tools, not toys. Agents need infrastructure designed for parallelization and isolation, not localhost hacks.

Strengths

  • Founders have deep credibility: shipped Gem, spent a year coding exclusively with agents, understand the workflow intimately
  • Solves a real constraint that gets worse as agents improve, localhost becomes a bottleneck, not a feature
  • Mobile app is a genuine differentiator; most dev tools ignore it, but if coding is 'just texting,' mobile matters
  • Snapshot-based isolation means agents can't break each other's work; clean separation of concerns
  • Slack integration and scheduled automations suggest they're thinking about workflows, not just UI
  • Market timing: Claude Code and Codex adoption is accelerating; infrastructure gap is widening

Risks

  • Requires users to trust their code and environment to a third party; security and privacy concerns are real, especially for proprietary codebases
  • Pricing model unclear, if it's per-agent-hour or per-compute, it could get expensive fast when agents run in parallel. Cost sensitivity could kill adoption
  • Dependency on Anthropic and OpenAI APIs; if Claude Code or Codex change pricing, UX, or availability, the product breaks
  • Onboarding friction: scanning and porting local dev setups to cloud is non-trivial; one bad port and users abandon it
  • Competitive response: Anthropic or OpenAI could build this themselves or integrate it directly into their products
  • Market size uncertainty: how many developers actually use Claude Code or Codex as primary tools today? Early adopters only, or mainstream?
  • Mobile app claim needs validation, is mobile coding actually viable for complex work, or is it a nice-to-have that doesn't drive retention?

Questions about this idea?

FlyBot reads the scoring and gives you a second opinion on “Boxes.dev: ditch localhost; run Claude Code and Codex in the cloud”.

Open FlyBot