{"version":"2.1.269","anchor":"new-circuit-breaker-category-claudesettingsfile-added-to-t","canonical_anchor":"new-circuit-breaker-category-claudesettingsfile-added-to-t","heading":"New circuit-breaker category \"claudeSettingsFile\" added to the safety-bypass rules table, marked host-person-only","tier":"internal","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/new-circuit-breaker-category-claudesettingsfile-added-to-t","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### New circuit-breaker category \"claudeSettingsFile\" added to the safety-bypass rules table, marked host-person-only\n\nA new claudeSettingsFile safety category is added, restricted to the host person only\n\n**What**\n\nClaude Code has an internal table controlling which categories of safety checks can bypass the normal permission system (referred to internally as the \"immune system\") or get routed to an automatic classifier instead of asking you directly. A new category, `claudeSettingsFile`, has been added to this table. Two new properties, `hostPersonOnly` and `localProjectionOnly`, were also added to every entry in the table, and `claudeSettingsFile` is the only entry currently marked `hostPersonOnly: true`.\n\n**Why**\n\nThis adds a distinct safety category specifically for changes to Claude's own settings file, and restricts it so only the host person (rather than, say, an automated actor) can act on it \u2014 tightening control over who can modify Claude Code's configuration.\n\n- Area: Permissions\n- Names: `claudeSettingsFile`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}