{"version":"2.1.281","anchor":"new-list-for-project-config-files-a-predicate-narrowed","canonical_anchor":"new-list-for-project-config-files-a-predicate-narrowed","heading":"New list for project config files; a predicate narrowed","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/new-list-for-project-config-files-a-predicate-narrowed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### New list for project config files; a predicate narrowed\n\nA check for one project config file name was narrowed, and the broader list of matching config file names moved into a separate check\n\n**Unclear.** The finding does not say which file name the narrowed check matches or which features use each check.\n\n**What**\n\nClaude Code has an internal check that recognises project configuration files by name. That check now matches only one config file name and its variants. The broader list, which includes names starting with `.config.json.` and other prefixes, moved into a new, separate check that also calls the narrow one.\n\n**Why**\n\nIn practice, places in Claude Code that want only the single config file and places that want the whole family of related files can now ask different questions."}