91–100 of 113 posts
Claude code has a version that runs on the cloud. You grant it access to Github then and you can tell it to make changes and create PR from your phone, tablet, or desktop. I'm curious, but what makes this difference than that?
Just checked the demo, it looks super interesting. how can i make sure, it doesnt burn through endless tokens / credits when i let it work independently? Thanks
The ralph loop mode also has the concept of a budget per task.
It's cool, and I completely get what you mean, I am curious to know how it differs from cloud agents by others like Cursor, Anthropic and Warp.
You are also free to swap/combine these harnesses as you please, which is something Anthropic can't do. For instance claude code implements and codex reviews.
I strongly believe all of these projects are unnecessary. Install LXC on a server Start a container called dev Add 25 lines to your zshrc I say dev1 and it spins up fresh Dev2 copies from that and is a fresh container. Auto uses tmux. Claude code with bypass mode. Do anything. Close laptop. Come back later. Even have a lock mode blocking all internet access except to the llm provider. Ssh key agent forwarding through…
However, once you want to trigger tasks from Slack, Linear, or GitHub issues or onboard teammates who aren't comfortable wiring up LXC + tmux + agent forwarding, a managed layer is needed.
I think we're at a moment where builders with great setups like yours and products like ours are feeding each other good ideas. The patterns you figure out in your zshrc inform what we productize, and the workflows we ship give you new things to try. It's a virtuous circle. Everyone should use the right-sized solution for their situation.
Congrats on the launch, the agentbox-sdk looks interesting, but seeing as the first commit was 3 days ago - I feel a little wary to use it just yet! One question, do you have plans for any other forms of sandboxing that are a little more "lightweight"? Also how do you add more agent types, do you support just ACP?
Thank you! agentbox-sdk is very recent so it is not stable just yet indeed! For the lightweight sandbox, can you give an example? Currently we support main coding CLIs, ACP support is not shipped yet.
For example Monty by the pydantic team, or the Anthropic sandbox which I believe uses OS level primitives.
I’ve been developing an open-source version of something similar[1] and used it quite extensively (well over 1k PRs)[2]. I’m definitely believer of the “prompt to PR model”. Very liberating to not have to think about managing the agent sessions. Seems that you have built a lot of useful tooling (e.g., session videos) around this core idea. Couple of learnings to share that I hope could be of use: 1) Execution sandbox…
I've also (separately) got a tool for local dev that sets up containers and does SSL interception on traffic from the agent, so it could also swap creds and similar.
The reason they're separate is that in a corp environment the expectation is very strongly that an email account = a human. You can't easily provision full employee accounts for AIs, HR doesn't know anything about that :) In my own company I am HR, so that's not a problem.
The biggest practical difference from cloud solutions: agents that run on your own machine can interact with your actual environment. Our agents browse the web, manage a Discord bot, push to git repos, and read email. They share a filesystem so one agent's output is another agent's input.
The tradeoff is obvious: no isolation, no scaling, and if your home server goes down, everything stops. But for a single developer who wants an AI that actually does things (not just produces PRs), local gives you reach that sandboxed cloud agents cannot.
The "prompt to PR" model is clean for dev work. For everything else (marketing, monitoring, data collection, content creation), agents need to touch the real world, and that is harder to sandbox.
I strongly believe all of these projects are unnecessary. Install LXC on a server Start a container called dev Add 25 lines to your zshrc I say dev1 and it spins up fresh Dev2 copies from that and is a fresh container. Auto uses tmux. Claude code with bypass mode. Do anything. Close laptop. Come back later. Even have a lock mode blocking all internet access except to the llm provider. Ssh key agent forwarding through…