31–36 of 36 posts
> One read-only command that inventories every AI agent, harness, MCP server, plugin, and AI extension on a machine If this tool is returning even a single hit from this, you're probably using these agents wrong. You really want to run these in a way so they cannot touch your system drive/general filesystem that you use to do real work on. Even SOTA models at the end of their context limit behave REALLY illogical and…
> One read-only command that inventories every AI agent, harness, MCP server, plugin, and AI extension on a machine If this tool is returning even a single hit from this, you're probably using these agents wrong. You really want to run these in a way so they cannot touch your system drive/general filesystem that you use to do real work on. Even SOTA models at the end of their context limit behave REALLY illogical and…
Came here to write this. Built my own harness with much better sandboxing, because I am using abliterated models for the implementations and they sure try to escape out of their sandboxes. A lot. The sandbox from other harnesses like e.g. OpenCode essentially is useless. They think parsing arguments alone to detect paths helps, and LLMs know that because they will just pipe data differently then to escape the path tr…
Mine pretends to be a local ACP agent, but it’s actually managing a Docker container and proxying the ACP connection into the container over websocket. You can specify a bunch of utility stuff in the YAML definition like directories to bind-mount, directories to copy from the host, scripts to run when the container starts, etc. You can also toggle whether ACP-native tools like read/write file and shells execute on your host or in the container (in container by default).
Works well, I forget whether I’m on that or pi-ACP directly until it spits out a time in the wrong timezone or I forget that it can’t check my DNS settings or something.
Really cuts down on the damage it can do. Mine is basically down to “it can delete my ~/.pi and the repo it’s working on” and that’s about it unless it can escape the container.
> One read-only command that inventories every AI agent, harness, MCP server, plugin, and AI extension on a machine If this tool is returning even a single hit from this, you're probably using these agents wrong. You really want to run these in a way so they cannot touch your system drive/general filesystem that you use to do real work on. Even SOTA models at the end of their context limit behave REALLY illogical and…
Earlier quoted context omitted.
This is the correct response, but it also feels as though ≈nobody is sandboxing their agents/harnesses in practice. Or at least, a good majority isn’t.
AFAIK, I know plenty of frontend engineers that without blinking run "npm install" on random 3rd party projects they find on GitHub, and they do their banking and everything else on the same machine. But then again, I also know people (one person to be fair) who have unprotected sex with prostitutes, so maybe something makes me slightly biased here.