Claude Code has gotten so bad about this that I’ve stopped using it for code reviews. I may look into wiring Claude up to Codex as an alternative LLM just to compensate. I think the issue is that I’m running Claude Code in a container so it sees that it is root, and becomes a lot more cautious. Not sure, though.
Show HN: Continue? Y/N: A 60-second game about AI agent permission fatigue
161–170 of 200 posts
Re: Show HN: Continue? Y/N: A 60-second game about AI agent permission fatigue
#162A bit too JavaScript specific... can't really play if you don't know that ecosystem.
Re: Show HN: Continue? Y/N: A 60-second game about AI agent permission fatigue
#163Re: Show HN: Continue? Y/N: A 60-second game about AI agent permission fatigue
#164The permission thing is a killer to productivity, if you're running Claude I think it's more efficient to just run in a disposable sandbox (like exe.dev[1]) or in some form of docker container with permissions you're personally ok taking the risk with on a personal machine[2] [1] - https://exe.dev/ is a new cloud provider with some very useful agent UX [2] - I built https://github.com/stanislavkozlovski/dclaude/ for…
A disposable sandbox wont protect you from secret exfiltration. Assuming you don't consider your code a secret, you could of course set up your sandbox so it doesn't have any secrets, but that would severely limit the kinds of tasks you can use the agent for.
Re: Show HN: Continue? Y/N: A 60-second game about AI agent permission fatigue
#165Re: Show HN: Continue? Y/N: A 60-second game about AI agent permission fatigue
#166Re: Show HN: Continue? Y/N: A 60-second game about AI agent permission fatigue
#167Re: Show HN: Continue? Y/N: A 60-second game about AI agent permission fatigue
#168Weird 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.
The whole premise IMO is pretty flawed. It's interesting as an ad for the company though.
Re: Show HN: Continue? Y/N: A 60-second game about AI agent permission fatigue
#169Claude Code has gotten so bad about this that I’ve stopped using it for code reviews. I may look into wiring Claude up to Codex as an alternative LLM just to compensate. I think the issue is that I’m running Claude Code in a container so it sees that it is root, and becomes a lot more cautious. Not sure, though.
If you're running Claude Code in a container anyways, why does `--dangerously-skip-permissions` not work for you?
Re: Show HN: Continue? Y/N: A 60-second game about AI agent permission fatigue
#170Fun game, but it showed the lack of security hygiene employed by the game writer. It said `cat ~/.zshrc` was bad because it would share tokens and secrets, but I would never put secrets into my shell rc.
Plenty of people would. But then I guess they're in env and probably already available to Claude