{"version":"2.1.285","anchor":"slash-commands-starting-with-a-path-like-name-no-longer-misp","canonical_anchor":"slash-commands-starting-with-a-path-like-name-no-longer-misp","heading":"Unknown slash commands are checked differently before being treated as file paths","tier":"notice","area":"Slash Commands","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/slash-commands-starting-with-a-path-like-name-no-longer-misp","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Unknown slash commands are checked differently before being treated as file paths\n\nTyping an unknown slash command now checks the name first and skips the file-path check for forms that are not local paths\n\n**Unclear.** What the two new checks look for is not known.\n\n**What**\n\nSlash commands are instructions you type starting with `\/`. When you type one Claude Code does not know, it used to always check your disk to see whether the text was really a file path. It now:\n\n- first checks whether the name is valid\n\n- skips the disk check for forms that are not local paths\n\n- drops commands that a new check flags\n\n**Why**\n\nThis affects what happens when you paste or type a path that starts with `\/`, and whether it is treated as a command or as a path.\n\n- Area: Slash Commands\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}