[BUG] --settings argument is disreguarded
Status Fixed / completed
Maintainer reply ✓ Yes — dicksontsai
Activity 10 comments · opened Sep 9, 2025 · closed Dec 17, 2025
💡 Likely answer: A maintainer (dicksontsai, collaborator)
responded on this thread — see the highlighted reply below.
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
When I run Claude code with the --settings argument, the provided settings are ignored. It's ignored whether it's a JSON string OR a path to a JSON file.
Example:claude --settings=/tmp/gitbutler-claude-settings.json
/tmp/gitbutler-claude-settings.json
{"hooks":{"Stop":[{"hooks":[{"command":"osascript -e 'display notification \"Nailed it\" with title \"Claude Code\" subtitle \"AI assistant\" sound name \"Glass\"'","type":"command"}],"matcher":""}]}}It seems like this regression was introduced in 1.0.94. The last working version we've found is 1.0.93.
The issue is prevalent when used with our streaming arguments in GitButler as well as passing --settings and using it through the TUI like in the provided example.
What Should Happen?
With this example hook, it should send a notification when claude has finished responding.
Error Messages/Logs
Steps to Reproduce
- Write
{"hooks":{"Stop":[{"hooks":[{"command":"osascript -e 'display notification \"Nailed it\" with title \"Claude Code\" subtitle \"AI assistant\" sound name \"Glass\"'","type":"command"}],"matcher":""}]}}into/tmp/gitbutler-claude-settings.json - Run
claude --settings=/tmp/gitbutler-claude-settings.json
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
1.0.93
Claude Code Version
1.0.109
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Other
Additional Information
_No response_
10 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
Issue
1.is talking about the merging behaviour (which is intended). This issue talks about--settingsnot working at all.2.and3.are different topics.Update:
After a random last ditch effort before we started merging our config into the main user's config, I typed
--settings XXXinstead of--settings=XXX, it now works!It seems like in 1.0.94 specifically the
--settingsargument stopped supporting having an=after it. The--mcp-configand--output-formatand others all work just fine with an=except--settingsnow.I can repro that
=doesn't work for--settingsspecifically due to the way we parse the flag.This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.
Commenting to keep the issue open. It was the cause of https://github.com/anthropics/claude-code/issues/13468
Any ETA on a fix for this very simple issue?
@dicksontsai Do you know when this might be fixed? Seems like a trivial thing
I merged in a fix that should go out in the next version. Sorry for the delay.
Thank you!!
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.