← All IntelClip / EntertainmentAuto mode security: route permission checks to a classifier
From Reflecting on a Year of Claude Code (Boris Cherny) · ≈7:21
“It's just human nature, when you accept 99% of requests, that your eyes just glaze over when you read it.”
“Just routing it to a different model and having it check for security works so much better.”
What’s in it
- How Claude Code's auto mode replaces manual permission prompts
- Why routing security checks to a model beats human review
- Argument that auto mode is safer than approving every prompt
Clip transcript
and I don't have to sit there and watch it. But from the very early stage we had this like permission prompts model for Claude Code, right? Like it runs a tool and then it asks you like, hey, are you okay running this tool? And you had to say yes or no. And at the time, that was kind of the best we had a year and a half ago because we didn't have, you know, classifiers. The model was not as well aligned as it is today. So auto mode was just such a it was such a big step up because actually you don't want to read most of these requests. Just routing it to a different model and having it check for security works so much better. Yeah. And if a thing like is a little suss or, you know, this isn't the command that you think you want to run or it's not safe, the model will just deny it. And then you can go back and you can allow it later. I think this has been one of those, like, step changes. We just, there's no way we could have done this a year and a half ago. It's just human nature, when you accept 99% of requests, that your eyes just glaze over when you read it. And so actually, we feel that auto mode is more safe than reading every single permission prompt, because it means that your only paying attention to the most important thing and not like being spammed a bunch of things that are just 99% yes. I think security is one of these things.
Comments
Sign in to comment.
Loading comments…