SaaS Metrics
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 building boxes.dev with boxes.dev for months and it’s honestly been a gamechanger. It’s hard to go back once you realize how much localhost has been limiting you; based on early feedback from beta testers, we’re increasingly sure that cloud is the future of agentic coding.We’d love for you to experience it yourselves! Would appreciate any feedback – and happy to answer any questions on this thread.
Show HN: Boxes.dev: ditch localhost; run Claude Code and Codex in the cloud
The first cloud-only ADE providing dedicated cloud compute and isolated environments for every coding agent (Claude Code, Codex), eliminating localhost limitations, resource constraints, and enabling parallel, mobile-first agentic development.
View Origin LinkProduct Positioning & Context
AI Executive Synthesis
The first cloud-only ADE providing dedicated cloud compute and isolated environments for every coding agent (Claude Code, Codex), eliminating localhost limitations, resource constraints, and enabling parallel, mobile-first agentic development.
Boxes.dev addresses critical infrastructure limitations for scaling agentic development. The shift from localhost to a cloud-only agentic dev environment (ADE) solves resource constraints, parallelization issues, and the need for isolated testing environments. By providing each agent with its own cloud computer and a snapshot of the full dev setup, it enables robust end-to-end testing and eliminates the overhead of managing local environments. This product signifies a market trend towards specialized cloud infrastructure for AI-driven development, recognizing that traditional local setups are insufficient for complex, concurrent agent workflows. The emphasis on mobile access and integrations further indicates a move towards ubiquitous, flexible agent development platforms.
Related Ecosystem & Alternatives
Discover adjacent products, open-source repositories, and developer tools sharing similar technical architecture.
Deep-Dive FAQs
What is Boxes.dev: ditch localhost; run Claude Code and Codex in the cloud?
Boxes.dev: ditch localhost; run Claude Code and Codex in the cloud is analyzed by our AI as: The first cloud-only ADE providing dedicated cloud compute and isolated environments for every coding agent (Claude Code, Codex), eliminating localhost limitations, resource constraints, and enabling parallel, mobile-first agentic development.. It focuses on Boxes.dev addresses critical infrastructure limitations for scaling agentic development. The shift from localhost to a cloud-only agentic dev envir...
Where did Boxes.dev: ditch localhost; run Claude Code and Codex in the cloud originate?
Data for Boxes.dev: ditch localhost; run Claude Code and Codex in the cloud was aggregated directly from the Hacker News community ecosystem, representing raw developer and early-adopter sentiment.
When was Boxes.dev: ditch localhost; run Claude Code and Codex in the cloud publicly launched?
The initial public indexing or launch date for Boxes.dev: ditch localhost; run Claude Code and Codex in the cloud within our tracked developer communities was recorded on June 5, 2026.
How popular is Boxes.dev: ditch localhost; run Claude Code and Codex in the cloud?
Boxes.dev: ditch localhost; run Claude Code and Codex in the cloud has achieved measurable traction, logging over 85 traction score and facilitating 63 recorded discussions or engagements.
Which technical categories define Boxes.dev: ditch localhost; run Claude Code and Codex in the cloud?
Based on metadata extraction, Boxes.dev: ditch localhost; run Claude Code and Codex in the cloud is categorized under topics such as: cloud-only agentic dev environment (ADE), Codex, Claude Code agent, cloud computer.
How does the creator describe Boxes.dev: ditch localhost; run Claude Code and Codex in the cloud?
The original author or development team describes the product as follows: "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..."
Community Voice & Feedback
Hello gents, some quick feedback.I think when you say “ditch localhost” you’re telling me to ditch my fast, instant-response laptop which I own and can peg the CPU of 24/7 for $0, in favour of a tiny cloud VM that I rent forever.Your infra to run agents and builds for me is compared in my mind to a shell script an agent wrote a year ago and I reviewed once, that fires up my dev server and a local psql (5-10mb ram) on a dynamically allocated port hashed off the name of my current worktree, which it does so it doesn’t clash with other parallel work.When the internet slows or dies I rarely notice.As a cost conscious person who likes it when letters appear as I type, I think I might not be your ICP.Am I being an asshole? Maybe. Am I going out of my way to tell you what goes on in the minds of people like me when we see offerings like this? Also maybe.
It would be nice if there is an extension for VSCode or its forks that let you monitor your agent *running inside* your local machine, or VSCode adds support for it. I want to run agents on the codes I have open, not pushing them to a cloud "box" to run agents on there. But I do like being able to monitor or pick up the next steps from my phone.Last time I tried to let AI build such extension, it told me that VSCode did not expose extension API to monitor AI chat.
What's the security story? I would love to adopt cloud dev environments that are constrained enough that I can safely run agents in YOLO mode, but not so constrained that they are useless. I would want it to be safe enough to run 80 to 90% of typical development work without supervision, and then have an escape hatch that allows doing other things with human supervision.edit: and if anyone knows of an existing service that has these properties, I'd love to know about it.
Really cool tool!I am building a self-hosted tool (OpenClaw-like) to solve the same problem (running agents 24/7 and access from monile), which I think is the main alterative approach to cloud tools. I'm glad that other people have recognized the problem.We currently use worktrees btw. We have a port allocation system that sends ports to the agent automatically, which suffices for smoke testing web projects in parallel but requires some configuration. We've also found that asking agents to find a free port works as well. There's no way to get security-relevant isolation without a containerized system, but everything else can be worked around, and IMO more easily than the setup required to make a project ready for VM/container development.
What kind of cpu/memory do the vms get? Is there a way to define the template that's used, so I can say to a new team member, log in to boxes.dev and all the repos and tools are already there for you? And where do you get the machines, can we bring our own? The orchestration layer and product experience ticks all the boxes for me but where Codex, Claude, and Cursor have fallen down for me in the past is:- slow and outdated vms- horrible/no way to standardize environments for my team- no way to bring our own compute to help resolve these issues ^
You can pry localhost from my cold dead hands.
This looks very clean, great job!If your CTO didn't spend the past year making an orchestration tool and a baby is he even qualified?I have a vibe-coded orchestrator that I use to manage my claude and codex sessions across multiple machines, can also spin up sprites from fly.https://github.com/tinkerer/propaneswarning: it is probably totally unsuitable for anyone else to use except for meThe main idea is a widget that you embed in your apps that lets you select elements, paste screenshots, and prompt what to change. This workflow is very productive for me. I would encourage everyone to add element selection to their orchestrators prompt composers. If you watch the looms on the readme note that my CLAUDE.MD calls me a Meat Computer and reminds me to hydrate.I have a native tauri version that lets you select UI elements through the macos accessibility api too.The session service uses tmux so you can open a native terminal via ssh and tmux attach. I add a ton of features that are in varying degrees of half-baked: the "brainstorm" mode allows you to do microphone transcription while interacting with the DOM and it will suggest tickets automatically. I've also been working on "bd2sdd" which is supposed to take your strings of user inputs and transform it into a spec, presumably because I also desired regressions. There are Wiggums (which aren't relevant anymore with /goal) and "FAFO swarms" (fan-out, aggregate, filter, optimze) which I use to reverse engineer other pieces of software, PowWow for codex and claude to work together.I stole the structured views and remote session control from my friend's Agent Portal project txcl.io which is more fully-baked and narrower scope than propanes.The ticketing system / tmux / structured views has been slowly evolving into multi-agent chat with a primary "Chief of Staff." It integrated pretty nicely into Slack.
I really like the pricing model and focus on not shafting people by auto-sleeping when an agent is done working.I’ve been working on an [OSS TUI](https://github.com/prettysmartdev/awman) for managing agent execution and workflows in containers (local or remotely) and would love to collaborate if you’re interested.
I might use this if it supported any old cloud or VPS, and was at most $10/mo. The fact that you have decided that this platform should only live in your own custom cloud is unappealing to me.Or, open source it and let us run it on our own VPS and keep your expensive cloud for those who want to pay. As it stands would never consider it.
Interesting. Given that OpenAI and Anthropic are steadily moving down the stack (e.g. remote execution, Codex desktop, Claude Code integrations), how do you think about defensibility? Do you expect the labs to eventually offer a cloud-native ADE themselves, and if so, what advantage do you think an independent platform retains?Also, do you see Boxes supporting OpenCode and self-hosted/local models in the future? If the rented machines have enough RAM and GPU access, it seems like there could be an interesting path toward a model-agnostic platform rather than being tied to the frontier labs.
Discovery Source
Hacker News Aggregated via automated community intelligence tracking.
Tech Stack Dependencies
No direct open-source NPM package mentions detected in the product documentation.
Media Tractions & Mentions
No mainstream media stories specifically mentioning this product name have been intercepted yet.
Deep Research & Science
No direct peer-reviewed scientific literature matched with this product's architecture.