{"version":"2.1.301","anchor":"safety-check-denial-gets-a-noconfighome-reason","canonical_anchor":"safety-check-denial-gets-a-noconfighome-reason","heading":"Safety-check denials can now record a missing config folder","tier":"internal","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/safety-check-denial-gets-a-noconfighome-reason","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Safety-check denials can now record a missing config folder\n\nWhen a safety check refuses a tool, Claude Code can now record the reason as a missing configuration home\n\n**What**\n\nA safety check is a point where Claude Code stops a tool from doing something risky. When it refuses, Claude Code labels the reason. Besides the label for blocked reads outside the allowed area, a second safety-check reason is now labelled `noConfigHome`. Before, such reasons got a generic label.\n\n**Why**\n\nRefusals that happen when there is no configuration home are now told apart from other safety-check refusals.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}