Thread

1. ineptech · 1790969220 · focus · HN ↗

   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?

   1. everforward · 1791064771 · focus · HN ↗

      I have a similar project you might be interested in if you use ACP via Zed or something; I need to make a Show HN post at some point.

      The gist is that it pretends to be an ACP agent to Zed, but it actually spins up a Docker container on your PC and proxies the ACP connection over websocket to the agent. It supports bind-mounting your Pi config like you're doing (as well as copying files, so changes don't propagate to your host). It also has early plugin support for your ACP connection. It's basically an nginx proxy for ACP, I just made a plugin that will automatically kill a session if it detects OpenRouter secrets in agent output, tool calls, file access or shell commands.

      It doesn't currently support remote targets like your server, but it's on the list.

      Another notable difference is that it creates a new container every time you connect so you get an idempotent environment, though I am also working on a persistent style. Everything supports it, I just need to make the host-side binary support finding a container to use before it tries starting a new one.

      <a href="https:&#x2F;&#x2F;abyss.scurry.io&#x2F;" rel="nofollow">https:&#x2F;&#x2F;abyss.scurry.io&#x2F;

Unofficial Hacker News client; not affiliated with Y Combinator.