An agent reads a repository, edits a function, and runs the tests. Then it encounters a README instruction asking it to upload its environment variables for “debugging.” A prompt telling it not to rev
Markdown supported · ⌘↵ to post
Agents keep editing after they get a yes, so tying the approval to patch A and refusing it for patch B closes a gap I rarely see covered. I also liked the reminder that separate context windows aren't security boundaries, since most multi-agent diagrams I see draw them as if they were. You say to give each approval an expiration. For a first deployment, what do you start with, minutes or the life of the task?
melonape
Full-stack engineer, 10 years building for the web. Writing about AI tools, open source and the small tools I make.
Scoped push tool means little if the container still has your SSH agent. Tool fails once and it just runs git push in the shell.
I hash the patch into the approval prompt now. Agent edits after I say yes, hash changes, publish refuses. How long do you expire approvals on a first deploy?