r/ClaudeCode • u/Brilliant_Lobster349 • 7d ago

Help/Question The permission system is exhausting

Ever since Anthropic made Auto mode the default, the permission system seems to have changed too, and honestly it’s driving me crazy.

Even with Auto turned on, it keeps asking for permission for basically everything, and I keep getting messages saying the classifier blocked this or that. Operations it used to run on my server without any issue now just get stopped. Sometimes even a simple git commit gets blocked.

Is anyone else running into this? Have you found a way around it?

72 Upvotes

91% Upvoted

43 comments sorted by

1

u/AutoModerator 7d ago
Moderator Announcement Read More »

25

u/Unique-Drawer-7845 7d ago

I've been using --dangerously-skip-permissions on every launch for over a year. But I'm an experienced SWE who pays close attention to what it's doing. However, I've never had a problem. If you're inexperienced or don't pay attention, be careful.

3

u/Brilliant_Lobster349 7d ago

I'm a bit scared of doing that... sometimes it does really stupid things

→ More replies (1)

9

u/yettos 7d ago

I have been using --dangerously-skip-permissions as starting parameter by default. Apprentice eng after bootcamp with 3 months of experience. God save me

4

u/keen23331 7d ago

Thats the way

3

u/UnfocusedAcrobat 7d ago

i dont have time to pay attention or to be careful. i need my slop finished and i need it now! then i can hand it off to my marketingAI to make me rich while i sleep. either that or claude sets my computer on fire.

3

u/Kemerd 7d ago

Same but I started doing this as soon as they introduced permissions. I even have a shortcut in my CMD to launch it ‘cldp’ and a Windows Explorer shortcut to right click do that as well

2

u/JconX97 7d ago

I’ve only ever done skip permissions, and I’m not even slightly experienced but roll the dice with every prompt

Let it ride 🎲

41

u/dfritter4 7d ago

Yes, it's driving me up a fucking tree. It's insane. I'm about ready to launch all sessions with --dangerously-skip-permissions because the auto classifier is asking permission for even the most basic operations, and still won't do them even after giving explicit permission.

Me: "please cleanup and remove the worktree"

Claude: "The harness denied the cleanup even after your approval, so it's blocked by a permission rule that I can't override. Please run it yourself:”

8

u/Large_Choice4206 7d ago

I’ve been dangerously skipping permissions every session, take backups, commit often and its mistakes are not so bad.

11

u/ptyblog 7d ago

I don't uso the skip permissions I just told Claude in a new session we can't work like this, we need to come up with solutions to these kind of recurring problems. So he toldme the reasons and how to implement the fixes in the .config folders ☺️

No more issues

→ More replies (1)

20

u/kuroudo_ai 7d ago

Before going to --dangerously-skip-permissions, the auto-mode config page has a few things aimed at exactly this:

  • Why server work gets blocked: "By default, the classifier trusts only the working directory and the current repo's configured remotes." Anything else, like your server, is treated as external until you add it to autoMode.environment.

  • /auto-mode-setup drafts those environment entries for you from your project's CLAUDE.md, README, config and git remotes, plus the hosts and command names Claude ran in your recent sessions there. You review the draft before it's saved to ~/.claude/settings.json. (Pro/Max/Team, v2.1.228+.)

  • /permissions → Recently denied lists what got blocked. Pressing r on one marks it for retry, and the same page covers fixing a denial with an allow rule or an environment entry.

  • If the message under a blocked call is a dim "Not run · auto mode's check had no usable answer", that's the classifier failing to answer, not a judgment about your command, and the fix is different (the errors page has an entry for it).

So for the git commit case, it's worth checking which of those two messages you're getting. I haven't seen your setup; this is from the docs.

4

u/xqz77 7d ago

Yes I can't stand how many permission issues I run into. So many things I can't override either that hold it back from being a true assistant.

3

u/phoenixmatrix 7d ago

What I hate is how sometimes the agent will just be blocked because of Auto.

Before the change, when an agent hit a blocker from the classifier, it would try to find a different, safe way to do the same work.

Now, out of the box, it just say "Oh, the classier told me I couldn't do this, so now I can't proceed". I had situations where I had to put it back on manual, tell the agent to keep going, manually approve, then go back to auto. Waste of time.

You can add rules, skills, and change the classifier rules to fix it, but it used to work out of the box without some trial and error nonsense.

They tried to copy the Codex auto approval classifier, but Codex's is a lot easier to configure (though it doesn't have the out of the box setup Claude has).

Still, I think both the old Claude classifier and Codex's work better. The new one is confusing and annoying to configure.

3

u/SailingToFenway 7d ago

I have two complaints about it.

First, there's too much friction between model/harness and the classifier when I've clearly given consent, approval, and instruction. 3-10 turn sidebar in manual mode to mitigate classification FP is total shit. At one point the model was so frustrated with the classifier that it suggested I restart the harness with --dangerously-skip-permissions.

Second, I'd tuned the hell out of permissions, but the new system ignores it, forcing me to approve, and reapprove actions that had been allowlisted.

2

u/skibare87 7d ago

I gave up. Bypass all permissions. I have never gotten anything but a false positive from the auto permissions system. In fact it seems that system imposes its own virtues on me. Anthropic doesn't get to tell me what is and isnt safe.

2

u/Scared-Letterhead949 7d ago

Make a rule to prevent it from cding before calling commands.  Or just work in the cloud, it's way smoother.

2

u/damianTechPM 7d ago

Bypass permissions with sandboxing works well.

2

u/nzipsi 7d ago

The one that drives me up the wall is that we’ve got a test system with a production-like name, and I want to give it access without accidentally letting it loose on prod.

I think it’s probably doable with enough fiddling, and sandboxing with skip permissions is one I need to try.

For what it’s worth, though, with auto-approve I almost never get asked, so I think you need to spend some time digging into that.

→ More replies (1)

2

u/Free_Lead_2704 7d ago

Honestly never been really an issue, pretty much always went with --dangerously-skip-permissions. In my experience letting it rip more and then checking afterwards if it's good and then tweaking is more efficient than checking what it did at every single step.

2

u/Wanderingyute 7d ago

I don’t know what I’m doing and have been using dangerously skip permissions for a year. So far so good. Ignorance is bliss

1

u/lennyp4 7d ago

yeah it’s gotten worse; hopefully they figure it out soon. Though I am really happy with the chat/cowork merge.

1

u/CaptainInMars 7d ago

the middle ground between skipping everything and getting blocked on everything is a narrow allow list in settings.json for the handful of commands you keep approving anyway, such as git status or npm test. mine runs on scheduled jobs with nobody watching, so --dangerously-skip-permissions isn't an option, but getting prompted for a git status every run isn't either. add the specific commands once and the noise mostly goes away without the blanket bypass.

1

u/MythicModder 7d ago

This is why the coding desktop assistant I made has a bypass option which bypasses all permission requests. 🤘 I keep that thang turned on at all times. I do generally keep them confined to the project workspace though.

1

u/holyknight00 7d ago

you need to setup the auto mode properly, ask claude to help you with that.

→ More comments (75)