Live data from Hacker News

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

boxes.dev

81–87 of 87 posts

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

#81
post #29
post #7

Earlier quoted context omitted.

A few angles to this. One is that coding just went through a massive change over the past year, that is not yet fully settled. Remember when everyone insisted on using IDEs and seeing the code with a chat sidebar? It's hard to argue you'll still be reading code a year from now. And even today, most people are still developing locally, which we're betting will shift to the cloud over the next few years. I imagine othe…

Maybe I'm in the minority but I still program with an IDE and a chat window in the side at work, as well as when I work on side projects. I do like to actually see the code that is getting produced.

I believe this to actually be the silent majority. But of course our job is object to a lot of changes right now and people are nervous what the "next job" will look like. You can hold position like me and just take the the new tools when they are well tested and integrated, be pragmatic about it. Fingers crossed!

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

#83

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.

you may checkout sandboxd project, it allow you ti run on your own vps plenty of sandboxes for differents usages : https://github.com/tastyeffectco/sandboxd

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

#84

This is cool, I'll check it out. Do you guys think that there will still be some work that is done locally vs the cloud, how are you thinking about the split from what you've seen developers doing? I also agree with the fact that git worktrees can be super frustrating to manage especially across multiple agent sessions.

Thanks! Longer term it's hard to say if everything 100% moves to the cloud. I'd guess that some things stay local (e.g. if you need your local hardware or are very are hands-on iterating with the code). But at the moment the average developer coding with AI seems way too local-bound, so we're focused on making remote development more convenient. At some point down the road we may add local as an option too.

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

#85

The mobile angle is the smart bit here, coding really has become just texting. How do you handle cost on idle boxes?

Thanks! We aggressively spin down idle boxes. We'll put any box to sleep where the agent has finished its turn and you're not connected, and then we'll wake it again if you connect (firecracker VMs can sleep/wake very quickly). We don't charge for sleeping boxes (neither does our infra provider) so this keeps costs down for everyone.

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

#86
post #47
post #43

Don't Anthropic and OpenAI both offer the same thing built in? What are the difference with this service?

their product attempts to duplicate your local dev setup on a machine on the cloud, which means they copy your .env / local postgres db, local docker-compose stack etc. It worked quite well for me, I tried it just now (except for postgres + setting up git). I think the product is quite good but still needs a bit of polishing. I'm a bit frustrated that they restrained EU users from downloading their app, but I guess t…

As a quick update, the app should be available in the EU now! Sorry about that.

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

#87

This is cool, I'll check it out. Do you guys think that there will still be some work that is done locally vs the cloud, how are you thinking about the split from what you've seen developers doing? I also agree with the fact that git worktrees can be super frustrating to manage especially across multiple agent sessions.

Thanks! Longer term it's hard to say if everything 100% moves to the cloud. I'd guess that some things stay local (e.g. if you need your local hardware or are very are hands-on iterating with the code). But at the moment the average developer coding with AI seems way too local-bound, so we're focused on making remote development more convenient. At some point down the road we may add local as an option too.

Got it that makes sense!
Post reply on HN