You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
SettingsArea: what it touches
ImprovementsKind: in v2.1.273,
ImprovementsSection of the release
What
Claude Code can now detect when settings keys are configured in a managed-settings file whose source doesn't apply for those particular keys. When this happens, it shows a new warning that names the specific source file, lists every offending key, and tells the user to either remove them or move them to a settings source that does apply, pointing to /status (the Settings interface, on the Status tab) to see the list of settings sources.
Why
This surfaces settings that are silently being ignored because they're defined in the wrong place, so users can find and fix misconfigured settings instead of wondering why a setting isn't taking effect.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added sinceA small documentation edit on Manage costs effectively touched a line naming /status after this was published.For a response from the Claude API billed at the 1.1× [data residency rate](https://platform.claude.com/docs/en/about-claude/pricing#data-residency-pricing), Claude Code multiplies the list price of that response's tokens by 1.1 in the ses…costssee the edit
Confirmed sinceAnthropic's documentation has since written up /status, on Claude Code changelog.* Fixed `/status` not showing the `apiKeyHelper` failure that its own error banner told you to checkchangelogsee the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up /status, on Claude Code changelog.
