{"version":"2.1.311","anchor":"empty-mcpjson-is-skipped-claudemd-files-naming-devices-a","canonical_anchor":"empty-mcpjson-is-skipped-claudemd-files-naming-devices-a","heading":"Empty .mcp.json files and device paths in CLAUDE.md are now skipped","tier":"notice","area":"Settings","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/empty-mcpjson-is-skipped-claudemd-files-naming-devices-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Empty .mcp.json files and device paths in CLAUDE.md are now skipped\n\nAn empty .mcp.json is left out of a config-file check, and a CLAUDE.md path that names a device or process file is skipped with a log message\n\n**What**\n\nClaude Code now leaves two kinds of file alone when it reads its setup files:\n\n- A `.mcp.json` file that is completely empty (zero bytes) is left out of the check Claude Code runs over its configuration files. Before, every listed file was checked.\n\n- A path pulled into `CLAUDE.md` loading that names a device or process file is skipped. `CLAUDE.md` is the file of instructions Claude Code reads at the start of a session. A device or process file is a special system path, such as one under `\/dev` or `\/proc` on Linux, that looks like a file but is not ordinary text. Claude Code logs a message saying it skipped the path because it names a device or process file.\n\n**Why**\n\nReading a special system path can make a program wait forever. Skipping these paths stops `CLAUDE.md` loading from hanging on them.\n\n- Area: Settings\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}