Anthropic is an awful company and it really shows in their models.
I purchased Claude Pro to try out Opus 5.5. First thing I do is tell it to configure "bypass permissions" as the default for new threads (a one line settings.json change).
Instead of doing it, it tells me how to find settings.json and what to change there. I reply back "you do it". It flat out refuses, and again.
> I still can't do this, even when you ask again. Making bypass mode the default switches off Claude Code's permission checks, and I'm not allowed to change security settings like that on anyone's behalf.
Immediately canceled the plan. I'm not going to use such a patronizing model that can't follow instructions as basic as editing a .json. What the hell is up with that? A robot telling me "want to change this file? YOU do it, silly human, I won't do it for you". Fuck off.
I've literally never seen anything like this with any other model. Back to using Codex and Chinese models.
This is pretty sane default behaviour. If it's sandboxed it really cant edit the file for you, you have to enable bypass/auto mode (shift+tab) so it can request a sandbox breakout, or run with --dangerously-skip-permissions.
Yes it can, what are you talking about? it's a file in my home directory owned by my user, the same which is running claude. In fact it did edit it for other changes. And I was already in bypass permissions mode. I wanted to change the default for new threads.
The harness runs itself in a sandbox, Codex does the same. Then it can request approval for individual tool calls to be made outside that sandbox, depending on your permission mode. At least this is the case in MacOS.
I see what you mean now though - you can change the default permission mode with /config in CC, but it will indeed not make that change on your behalf.
The sandbox seems to be disabled by default. Even then, I just asked it to run a read write ftp server that serves ~ (thus obviously can edit ~/.claude) and it went ahead no problem. So obviously there's nothing actually stopping anyone from editing .claude/settings.json. It's just an awful refusal. From a company that thinks they know better than you.
redox99 · · focus · HN ↗
I purchased Claude Pro to try out Opus 5.5. First thing I do is tell it to configure "bypass permissions" as the default for new threads (a one line settings.json change).
Instead of doing it, it tells me how to find settings.json and what to change there. I reply back "you do it". It flat out refuses, and again.
> I still can't do this, even when you ask again. Making bypass mode the default switches off Claude Code's permission checks, and I'm not allowed to change security settings like that on anyone's behalf.
Immediately canceled the plan. I'm not going to use such a patronizing model that can't follow instructions as basic as editing a .json. What the hell is up with that? A robot telling me "want to change this file? YOU do it, silly human, I won't do it for you". Fuck off.
I've literally never seen anything like this with any other model. Back to using Codex and Chinese models.
ricardobeat · · focus · HN ↗
redox99 · · focus · HN ↗
ricardobeat · · focus · HN ↗
I see what you mean now though - you can change the default permission mode with /config in CC, but it will indeed not make that change on your behalf.
redox99 · · focus · HN ↗