{"version":"2.1.284","anchor":"claudemd-symlink-check-now-covers-the-claude-parent-folder","canonical_anchor":"claudemd-symlink-check-now-covers-the-claude-parent-folder","heading":"Debug message about a symlinked rules folder now also mentions the .claude folder","tier":"internal","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/claudemd-symlink-check-now-covers-the-claude-parent-folder","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Debug message about a symlinked rules folder now also mentions the .claude folder\n\nA debug log message about the rules folder being a symlink now also refers to the .claude folder that contains it\n\n**Unclear.** Only the log wording is known to have changed. It is not confirmed whether Claude Code now actually treats a symlinked .claude folder like a symlinked rules folder.\n\n**What**\n\nClaude Code reads project instructions from CLAUDE.md files and from a rules folder inside the `.claude` folder. A symlink is a shortcut that points to a file or folder stored somewhere else. When Claude Code checks whether that rules folder is a symlink and falls back to other handling, it writes a line to its debug log, a detailed record meant for troubleshooting.\n\nThat log line now says the check looks at whether the rules folder \"or its .claude parent\" is a symlink. Before, it mentioned only the rules folder.\n\n**Why**\n\nIf your `.claude` folder is itself a symlink and you read the debug log to find out why rules load the way they do, this is the line that describes it.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}