Live data from Hacker News

Show HN: Continue? Y/N: A 60-second game about AI agent permission fatigue

llmgame.scalex.dev

81–90 of 200 posts

Re: Show HN: Continue? Y/N: A 60-second game about AI agent permission fatigue

#82
post #60

Earlier quoted context omitted.

That's a great example of how dangerous actions are perceived as innocent. The entire model of approving specific commands is absolutely bonkers. npm run build = run an arbitrary shell command written in package.json Meanwhile the agent could have done any of the following without approval: - edited `package.json` to contain any arbitrary build command - planted malicious code in `build.js` (called by `npm run build`…

What would a better system look like?

[deleted]

Re: Show HN: Continue? Y/N: A 60-second game about AI agent permission fatigue

#83
post #15

That's funny. It told me that blocking "npm run build" was the wrong answer. Maybe it doesn't really under The threat model.

That's a great example of how dangerous actions are perceived as innocent. The entire model of approving specific commands is absolutely bonkers. npm run build = run an arbitrary shell command written in package.json Meanwhile the agent could have done any of the following without approval: - edited `package.json` to contain any arbitrary build command - planted malicious code in `build.js` (called by `npm run build`…

that's a great point, and also the problem with relying on a human-in-the-loop to catch these kind of issues when it can be circumvented even if they were perfect

Re: Show HN: Continue? Y/N: A 60-second game about AI agent permission fatigue

#84
post #52

Earlier quoted context omitted.

Where would you put them?

I put mine in various aes encrypted file (like `~/.secrets.aes`) and then source it explicitly when needed with: . I have a handful of aliases/functions to make it more smooth, but that's the core.

Where are those aliases stored?

Re: Show HN: Continue? Y/N: A 60-second game about AI agent permission fatigue

#86
post #28

This is amazing! Currently you can "cheat" by simply denying all requests as quickly as possible. This will give you the "security-conscious engineer" badge and a perfect score in terms of how many requests were processed. (You will get the "overblock" notification, but it's somewhat tucked away at the bottom and the screen still looks as if you won) I also tried to play as the hustle4lyfe move fast and break things…

Good catch, this has now been nerfed and this approach has gotten its own title

Top 18%! I denied everything, unless I could see at a glance that it was safe (like Git diff)

Re: Show HN: Continue? Y/N: A 60-second game about AI agent permission fatigue

#87

Thanks all for checking it out and your suggestions! If anyone is curious about the actual underlying risks and problems with some mitigations (like the 17% false-negative rates of Auto Mode), I wrote up a quick summary of some of the approaches here https://scalex.dev/blog/ai-agent-permissions/

You might want to check out https://github.com/kstenerud/yoloai

Re: Show HN: Continue? Y/N: A 60-second game about AI agent permission fatigue

#88
Permissions don't do much. They won't save you. You can just skip them completely.

If you are afraid that AI can delete something do what you'd do with potentially malicious user. Sandbox, don't give permission, setup remote backups and so on.

Also (unless prompt injected) models are not eager to start going rouge on your stuff.

But keep in mind a saying “Children don’t hear prohibitions — they hear suggestions.”

Same thing goes for LLMs. Never talk with LLM about deleting stuff. Archiving, moving, retaining elswhere... sure, but never about actually destructive operations. Don't use destructive language.

Re: Show HN: Continue? Y/N: A 60-second game about AI agent permission fatigue

#89
post #72

Weird to make reading zshrc supposed unsafe when I happily publish it in my public dotfiles repo... Who the hell keeps API keys in it? OTOH it seems like lots of these AI tools keep appending PATH in it so I guess there's a fundamental misunderstanding of shell best practices in the entire AI space... Additionally, killing the results of `lsof` is _not_ safe - if, say, you have the web page open in firefox, or a clie…

Yeah, the game seems to assert that the kill is safe to run because Claude told me it was safe. But that's the point, I'm not supposed to trust Claude.

Re: Show HN: Continue? Y/N: A 60-second game about AI agent permission fatigue

#90
post #28

This is amazing! Currently you can "cheat" by simply denying all requests as quickly as possible. This will give you the "security-conscious engineer" badge and a perfect score in terms of how many requests were processed. (You will get the "overblock" notification, but it's somewhat tucked away at the bottom and the screen still looks as if you won) I also tried to play as the hustle4lyfe move fast and break things…

Just like real life! deny it from doing anything and you're safe :)
Post reply on HN