Move all Claude Code settings to user-settings and global-config#400
Merged
Conversation
The dedicated root YAML keys duplicated settings.json fields under toolbox-specific kebab-case names, splitting one configuration surface across two naming conventions and two write paths.
user-settings now carries raw settings.json content and global-config carries raw ~/.claude.json content, with known built-in keys validated fail-fast (value shapes, camelCase naming, section placement) in both the runtime script and the Pydantic model via parity-tested shared constants.
In isolated environments the user-settings content is built into ~/.claude/{cmd}/config.json, which the launcher passes via --settings, so profile settings keep outranking a repository's project settings and the toolbox does not write the isolated settings.json.
Auto-update and IDE-extension controls now target global-config, user-settings.env, and os-env-variables.
The permissions defaultMode enum gains auto, dontAsk, and delegate, and the max effort level accepts Sonnet models.
BREAKING CHANGE: the root YAML keys model, permissions, attribution, always-thinking-enabled, company-announcements, env-variables, and effort-level are no longer supported and are reported as unknown keys.
Migrate them into the user-settings section using camelCase settings.json names: model, permissions (defaultMode, additionalDirectories, allow, deny, ask), attribution, alwaysThinkingEnabled, companyAnnouncements, effortLevel, and env replacing env-variables (values must be strings, or null to delete).
env-variables is no longer a valid merge-keys entry; list user-settings instead to deep-merge env across inherited configs.
A CLAUDE_CONFIG_DIR isolation-directory override belongs in user-settings.env.
Coverage report
Click to see where and how coverage changed
This report was generated by python-coverage-comment-action |
||||||||||||||||||||||||||||||||||||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The dedicated root YAML keys duplicated settings.json fields under toolbox-specific kebab-case names, splitting one configuration surface across two naming conventions and two write paths. user-settings now carries raw settings.json content and global-config carries raw ~/.claude.json content, with known built-in keys validated fail-fast (value shapes, camelCase naming, section placement) in both the runtime script and the Pydantic model via parity-tested shared constants. In isolated environments the user-settings content is built into ~/.claude/{cmd}/config.json, which the launcher passes via --settings, so profile settings keep outranking a repository's project settings and the toolbox does not write the isolated settings.json. Auto-update and IDE-extension controls now target global-config, user-settings.env, and os-env-variables. The permissions defaultMode enum gains auto, dontAsk, and delegate, and the max effort level accepts Sonnet models.
BREAKING CHANGE: the root YAML keys model, permissions, attribution, always-thinking-enabled, company-announcements, env-variables, and effort-level are no longer supported and are reported as unknown keys. Migrate them into the user-settings section using camelCase settings.json names: model, permissions (defaultMode, additionalDirectories, allow, deny, ask), attribution, alwaysThinkingEnabled, companyAnnouncements, effortLevel, and env replacing env-variables (values must be strings, or null to delete). env-variables is no longer a valid merge-keys entry; list user-settings instead to deep-merge env across inherited configs. A CLAUDE_CONFIG_DIR isolation-directory override belongs in user-settings.env.