I Put a Setting in My Project Config and It Did Nothing

Description and use

Adding a key to the project config had no effect because the key is scoped to a different config file. Moving it to the correct file fixes the issue.

Adding a setting to a project‑level config file had no effect because the key is scoped to a different configuration file.

Correctly scoping settings eliminates silent failures and ensures configuration changes take effect.

Identify the setting key to change (e.g., autoMode).
Check the settings reference table for the key’s scope.
If the key is user‑scoped, move it to ~/.claude/settings.json or a managed config.
If the key is project‑scoped, keep it in .claude/settings.json.
Run npx @quintetkit/ccheck to validate scopes and detect misplacements.
Adjust the configuration file based on the checker’s output.
Commit the corrected config and verify the setting takes effect.

"autoMode" applies from user or managed settings only. It has no effect from this file.

71 of 223 keys are scoped.