{"version":"2.1.283","anchor":"loopmd-read-asynchronously-a-directory-named-loopmd-count","canonical_anchor":"loopmd-read-asynchronously-a-directory-named-loopmd-count","heading":"\/loop treats a folder named loop.md as no file","tier":"notice","area":"Slash Commands","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/loopmd-read-asynchronously-a-directory-named-loopmd-count","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### `\/loop` treats a folder named loop.md as no file\n\n`\/loop` now ignores a folder called loop.md and handles project and user loop.md files in the same way\n\n**Unclear.** It is not clear how the earlier version handled a folder named loop.md or other read errors.\n\n**What**\n\nWhen you run `\/loop` without a prompt, Claude Code looks for a `loop.md` file to use instead. It checks the project's `.claude\/loop.md` first, then the `loop.md` in your user configuration. The way it reads these files has changed:\n\n- a folder named `loop.md` now counts as no file\n\n- both files are trimmed and cut to length in the same way, where before the user one was handled separately\n\n**Why**\n\nFor most people nothing changes. The difference shows only in unusual cases, such as a folder that happens to be called `loop.md`.\n\n- Area: Slash Commands\n- Names: `\/loop`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5"}