You have an agent running on your local system. You want it to have access to a restricted set of things, both locally and remote. What is the technical mechanism you use to ensure that it has a subset of the access that you, as an individual logged into the same system, do?

(I am uninterested in "Don't run an agent" because while yes I see your point that doesn't mean it's not happening and security professionals have to deal with what's happening not what we want to be happening)

@mjg59 I'm using Patrick's addt for this https://github.com/jedi4ever/addt as the isolation, and clean environment each time (except for what I choose to add) convenient
@RichardoC @mjg59 ok I'll bite: this looks pretty neat right? run agents in containers, basic, nice wrapper. then you dig: second contributor is claude. should we trust agents to write a sandbox designed to contain agents?
@RichardoC @mjg59 i feel like we were pretty fast at going from "oh yeah, *you* still need to write the unit tests" to "bah the agent wrote the sandbox too, #thisisfine #loveskynet"