Ask HN: Secure wrapper for coding agents?

19 points by rjzzleep ↗ HN
I believe someone recently posted sort of a secure harness/wrapper for running coding agents in a secure sandbox. I can't find the project.

Of course I can make my own wrapper with systemd-nspawn, kata or bspawn, but I believe I saw a decently well-maintained project just a while back. Does anyone have a suggestion or link? It's become extremely hard to find things on GitHub with all the generated projects.

17 comments

[ 4.9 ms ] story [ 40.8 ms ] thread
I believe you're looking for Era. It uses libkrun for local microVM isolation and was built specifically to solve the "LLM hallucinated a destructive bash command" problem without the overhead of a massive VM.

Another one that handles this gracefully is Yolobox, which uses rootless Podman. Both are actively maintained and cut through the noise of the thousands of generic wrapper repos out there right now.

Have you thought About docker?
Docker has introduced sandboxes for this purpose.
for coding agents, i care less about sandbox branding and more about boring audit logs. what did it read, what did it write, and what was blocked?
This may be too naive, but I created a user on my linux box who doesn't have very many permissions. Then I sudo to that user, use firejail to start pi in a dev project directory, and let it have at it.

My projects are usually very limited with respect to external dependencies and that is part of prompts or markdown files describing various project goals, plans, and current state.

My operating theory is that this probably won't get my systems borked. I wasn't patient enough to dig deeper.

Beside from particular project, I would like to talk about my rule of thumb in agent usage, which is to separate “smart” from “authorized.”

That is, to build a state wrapper and separate agent from making runtime decision, a dangerous design is letting the same agent both decide and record the state of the system. If it hallucinates, you can hardly find the error.