[BUG] New --settings flag not working
Status Fixed / completed
Maintainer reply ✓ Yes — dicksontsai
Activity 11 comments · opened Jul 26, 2025 · closed Jul 31, 2025
💡 Likely answer: A maintainer (dicksontsai, collaborator)
responded on this thread — see the highlighted reply below.
Environment
- Platform (select one): Max plan
- Claude CLI version: 61
- Operating System: linux
- Terminal: alacritty
Bug Description
New --settings flag doesn't appear to work
Steps to Reproduce
┌─╼[130]╾─╼[09:39:54]
└─╼[~/code/dotfiles]
╰╼[main]╾─╼[4d99149]
▶ cat /tmp/settings.json
{
"model": "opus",
"permissions": {
"defaultMode": "plan"
}
}
┌─╼[09:39:55]
└─╼[~/code/dotfiles]
╰╼[main]╾─╼[4d99149]
▶ claude /model
╭───────────────────────────────────────────────────╮
│ ✻ Welcome to Claude Code! │
│ │
│ /help for help, /status for your current setup │
│ │
│ cwd: /home/mike/code/dotfiles │
╰───────────────────────────────────────────────────╯
╭─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ Select Model │
│ Switch between Claude models. Applies to this session and future Claude Code sessions. For custom model names, specify with --model. │
│ │
│ ❯ 1. Default (recommended) Opus 4 for up to 50% of usage limits, then use Sonnet 4✔ │
│ 2. Opus Opus 4 for complex tasks · Reaches usage limits faster │
│ 3. Sonnet Sonnet 4 for daily use │
│ │
╰─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
Enter to confirm · Esc to exit
┌─╼[09:40:24]
└─╼[~/code/dotfiles]
╰╼[main]╾─╼[4d99149]
▶ claude
╭───────────────────────────────────────────────────╮
│ ✻ Welcome to Claude Code! │
│ │
│ /help for help, /status for your current setup │
│ │
│ cwd: /home/mike/code/dotfiles │
╰───────────────────────────────────────────────────╯
╭─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ > Try "create a util logging.py that..." │
╰─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
? for shortcuts
Expected Behavior
Above I expect the model to be opus and the default mode to be plan mode
Actual Behavior
Neither setting is respected
Additional Context
I tried adding some hooks also but they didn't show up
11 Comments
I see the custom path in debug messages:
Also I checked and _only /tmp/settings.json exists out of those options.
Where do you specify
--settings? I seeclaude /modelbut notclaude --settings /tmp/settings.json /modelI screwed up. Apologies. Now that I look and do things correctly I see:
modelkey workspermissionsdoes not workhooksdoes not workBut since it's a new feature and not documented yet I have no good reason that's not the expected behavior. Is it?
Looks good:
They should work. What do you have in your separate settings file for those fields?
Possibly this is expected behavior but it would be nice if we can put anything that goes in a settings file normally and have it picked up.
Nothing:
Ok, I see the issue. Since the flag settings are read-only, they do not appear in the UIs. The "bug" here is the inability to display read-only settings. This may take a couple of releases to address.
Separately for hooks, there is a loading issue that needs to be resolved. I'll address this by the next release.
Hooks +
--settingsis now fixed as of v1.0.62.Appreciated!
On Mon, Jul 28, 2025, 9:52 PM Dickson Tsai @.***> wrote:
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.