I'm designing this for the student AI infrastructure here at Montana State, to avoid rolling out the current wild-west of local agents to our student body.
Wanting agents to act like you is wrong. You need to own that trust boundary. Build whatever tooling satisfies the contract that agents should have a “not”+<you> (or <you>+”-agent”) identity, and you actuate across that boundary explicitly.
For example, I have a second agent GitHub account that points at my human one. That allows me to write a trusted proxy that ACLs its identity tightly.
It cannot write to public repos ever. In the worst possible case, it externalizes to a private repo’s issue tracker. (Still has never happened in ~4 months)
Once you have this, you can let agents run free. But, it isn’t trivial to set up. Moreover, people don’t want to “do the work.”
All this assumes you abide by “never run untrusted agents on trusted hardware.”
For example, I store k8s credentials in 1pass and the cluster is only accessible via the network on my remote machine. I can grab the credentials from my laptop for the work I want to do on the remote, and never have to install 1pass on the remote machine.
Primary use case for lend wasn't agents when I started the project. It just was natural to add support for it after the fact.
Well, ideally, you would be giving the model direct access to a subset of what a given key enables- if fine grained access control for generated keys isnt available.