Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

  • Hacker News
  • Hi, I think I might be your target audience, I currently run pi on the server in my basement, in a minimalist docker container that gives it access to my code workspace and a config dir. Give me an idea what benefit I get on top of that by using the self-hosted pi pod?
  • Note: this does not appear to be a Kubernetes-based solution, the "pod" part just heavily sounds like it.
  • I've been working on a personal alternative harness to Claude Code and a very very small part of it was doing precisely this :) The project has been loads of fun.

    To be fair: I support sandboxing and microVMs.

    I'm pretty sure there's thousands of us, all implementing our own harnesses. The era of truly personal computing!

  • Interesting! Personally I'm not eager to spend tokens on having my own harness, sandbox etc. It's much much more feasible by spending tokens. But it does feel like a distraction and that I end up owning it. As in: a continuing distraction.

    So I've been experimenting for these purposes with omnigent as a way to be less locked into a single provider and for its sandbox abstraction. And I've also tried openshell for sandboxing. Hoping those two will keep improving.

  • Super cool! I have a similar system that incorporates Forgejo and Pi into a system that functions a little bit more like a software team: https://bakedpi.dev

    It's definitely more manual than some other solutions, but I prefer to know what my agents want to do before they do it.

    It's not exactly isolated in their own VMs though. It's using Docker which isn't the safest solution out there but also... well, it is what it is.

  • The barrier to create this myself is so low that 1: I can do it and 2: bad actors can do it. I’d like to use a shared tool that will get iterated on, but I just don’t want to risk it at this point given I can get “good enough” doing it myself.
  • I'll be sure to check this out but in the meantime, I'd like to ask: Isn't it generally a good practice to run coding agents in a VM? It provides a security boundary so that the agent is restricted to the VM.

    How does this compare? I see it's an "isolated sandbox", but what exactly does that mean?

  • Just ... use systemd nspwan ... stop reinventing the wheel ...

    it has all the options you would ever want, and is actually deeply aware of the kernel capabilities.

    every day someone comes with a new sandbox solution because they are too lazy to read one page documentation.

Explore Birbla archives