alt Hacker News> 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 does mistakes frequently. Don't run them straight on your machine unless you have backups and confirmed your backups work.
Replies
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.
I run it on a physically dedicated machine, it has a root there (through sudo nopassword) and I keep some of my stuff there too. I don't do it for security reasons, I just want it to run when my laptop is closed and I'm outside or what not.
Haven't seen any close calls so far. The thing just behaves. Nothing of the horror stories of eremerefing the whole home directory or a database. Am I just lucky?
"Even SOTA models at the end of their context limit behave REALLY illogical "
The trick is not go to that limit, but stay under 50% or even better 25% of context length. But backups are a smart thing anyway.
[flagged]
Aside from random errors made by the model, another reason to sandbox is that prompt injection could make your agent behave in an actively harmful manner.