Skip to content

Comment on Every Model Cheatsparent

Comments

Amen.

Why can’t we give agents a shell with permissions for programs and file system access controlled by Unix permissions?

This seemed to be a solved problem back in the systems where many users were logged into one machine and the admins had to keep everyone from impacting each other.

It would loose automagic?

In a recent full discloure I was reading about a CVE of an LLM agent, the vendor installed a “secure sandbox VM” and then just shared a host’s filesystem read/write to the agent’s VM.

We never solved the restricted shell problem for humans.

Can you elaborate?

Read, write, execute privileges on files and directories goes a long way. What's missing?

The biggest is Internet access, or networking in general, I suppose.

Two problems. First, it is remarkably difficult to come up with a set of programs that it is safe to let the restricted user use. Second, it is remarkably difficult to make the restricted environment useful enough if you're really serious about allowing only safe programs to be used. Try to make it useful enough and you end up with escapes everywhere.

Sure but then the file protections also apply to the programs used by the agent. If you can strictly limit the agent to only modifying files in the source code directory of a single repository, that greatly limits the blast radius of damage.

But that's not useful. That's the problem.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.