Live data from Hacker News

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

boxes.dev

31–40 of 87 posts

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

#31

Maybe I’m naive but the longest single workflow I ran was maybe 15 minutes. How do you steer agents to run “overnight”? And what is the quality of such execution?

Works well for very well defined task. If you have a really big feature like a front end migration, you can use /plan, and /goal which i think is in most harnesses. You can also use other tools that allow your agent to interact with other terminals(I use an ADE called orca) that has an orca skill where an agent can spin up different sessions(different from subtasks because they share the context and you can chose the harness/model unlike sub agents). Can also read from the terminal, use your browser or computer and task screenshots and after prepare a report or something.

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

#33
post #7

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…

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…

how can I short the we won't read code anymore bet?

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

#34
post #26

It feels somehow weird to see a cloud tool usable only from Macs. Oh well.

Sorry about that. We should have made that more clear in the post but unfortunately HN doesn't let us edit it anymore. We're just 2 people right now and wanted to ship early. We want to support other platforms over the long term. We are cloud, but there is a local component for porting your local environment for the fast onboarding, so it requires some care. Are you on Windows?

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

#35

You can pry localhost from my cold dead hands.

Lol ++. Although my local host for agent/codex stuff is a raspberry pi I connect to on LAN from my gaming/powerful desktop for sandboxing. However my use case seems to be the exact problem they are trying to solve! Might have to take a look into it at some point.

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

#40
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.

Post reply on HN