{"version":"2.1.317","anchor":"config-file-create-refusal-tracking-and-global-config-watche","canonical_anchor":"config-file-create-refusal-tracking-and-global-config-watche","heading":"Claude Code tracks when it declines to create its global config file","tier":"internal","area":"Internals","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/config-file-create-refusal-tracking-and-global-config-watche","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Claude Code tracks when it declines to create its global config file\n\nClaude Code now records when it declined to create its global config file during a run, and when a fallback read found no file\n\n**What**\n\nClaude Code keeps a global configuration file, where it stores settings that apply across all your projects. It now records two things about that file while it runs:\n\n- Whether it declined to create the file during the current run\n\n- Whether a fallback read of the file found no file at all\n\nClearing Claude Code's in-memory copy of the configuration resets the first of these. The watcher that notices changes to this file is now labelled `global_config`.\n\n**Why**\n\nThis is bookkeeping for the case where the configuration file is missing or unreadable. It most likely stops Claude Code from creating the file again when it should not.\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}