[BUG] Custom slash commands not discovered
Status Fixed / completed
Maintainer reply ✓ Yes — sid374
Activity 7 comments · opened Apr 2, 2025 · closed Apr 3, 2025
💡 Likely answer: A maintainer (sid374, contributor)
responded on this thread — see the highlighted reply below.
FIrst off, I almost always git-ignore my claude files. .claude is a dot-directory, so if Claude is trained to ignore it, then it does not seem to pick up on any of the slash commands that I add, even after refreshing sessions. I have a .python-version file and it was not able to provide a response based on that file until I told it to look there. Is this a default setting? OK, no problem if it is, but shouldn't this be documented? And shouldn't .claude/ files be excluded?? Claude is not picking up on the slash commands that I'm adding there.
7 Comments
@hesreallyhim just to confirm you are putting your custom slash commands in
.claude/commandsright as documented here?These should show up in the typeahead slash command menu when you type
/in the prompt inputYes, I'm putting commands in
./.claude/commandsand~/.claude/commands, once in a while i see they are registered and they populate the auto-complete but lately it seems like it hasn't been workingI'm almost always working from within a VS Code terminal, FWIW
Fix incoming in new version!
This seems to be working for me now! 🙏
Some observations:
CLAUDE.mdis given more weight. Example:Claude.md: Every response should start with the word "RESPONSE: ".claude/commands/say-hello.md: "Respond with the exact phrase, "Hello World!"So it "disobeys" the slash-command somewhat, but follows the
CLAUDE.mdmore strictly.This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.