[BUG] Custom slash commands no longer working
Status Fixed / completed
Maintainer reply None cached
Workaround ✓ Mentioned in thread ↓
Activity 14 comments · opened Sep 7, 2025 · closed Dec 9, 2025
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
Custom slash commands are no longer available on Windows.
I use custom slash commands frequently; they were very recently (9/5 I think), not today (9/7). They do not show on auto-fill and if I type in the command exactly I get "Unknown slash command: {rule-name}".
I have my commands in the .claude\commands folder of the repo.
I verified I opened Claude Code in the correct directory, and I tried with several projects. I tried also tried clearing the Users\{user}\.claude\projects folder, that also did not resolve.
May be related to https://github.com/anthropics/claude-code/issues/7271
What Should Happen?
I should be able to use custom slash commands.
Error Messages/Logs
Custom slash commands do not auto-fill when typing and if typed in fully Claude Code responds with "Unknown slash command: {rule-name}".Steps to Reproduce
- Have a custom slash command in the .claude/commands folder of your project.
- Attempt to use the custom slash command
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
1.0.108
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
Cursor
Additional Information
_No response_
14 Comments
I have been experiencing slash commands disappearing and then reappearing... for example, here is my current state with two sessions open within Warp Terminal on Mac.
Visible in this worktree:
<img width="1668" height="588" alt="Image" src="https://github.com/user-attachments/assets/ba8a0489-43b0-4c58-9462-f3353d5bdfbc" />
Try in a different worktree the 'start' slash commands do not appear:
<img width="1676" height="702" alt="Image" src="https://github.com/user-attachments/assets/6a87079d-422f-4db2-93b6-6a5f00035b28" />
Similar to https://github.com/anthropics/claude-code/issues/6657
Helpful work around for others who are experiencing this issue: Just ask claude code to use the intended command
Example: Use the @.claude\commands\launch-local.md command.
Had the same problem - custom commands AND agents not showing up in /help even though search was working.
Found the culprit was my ripgrep config. I had --color=always in my ~/.ripgreprc which was embedding ANSI color codes in file paths during Claude Code's
discovery process. It was trying to read files like [0m[1m[32m/path/to/command.md[0m instead of the actual path.
Fixed it by changing --color=always to --color=auto in my ripgrep config. Still get colors in terminal but Claude Code gets clean paths for file
discovery.
Worth checking if you have custom ripgrep settings - might be the same issue.
My slash commands have disappeared today. After Claude was restarted, they started to work normally again. Didn't change anything.
This is resolved for me with v2.0.1 🥳
They're not showing up for me at all now. Tried restarting claude. Multiple terminals. What a pain.
This was it for me. In my case it was
--prettyin my ripgrep config.It happens sometimes even in v2, but restarting the app usually helps.
It is finally working for me after setting
USE_BUILTIN_RIPGREP=0On Raspberry Pi 5 with Debian 12 (Raspberry Pi OS Lite) and Claude Code v2.0.24: same problem.
Solved by installing ripgrep:
sudo apt install ripgrepAnd adding in ~/.bashrc:
export USE_BUILTIN_RIPGREP=0then
source ~/.bashrcThis issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.
I am no longer experiencing this issue and haven't for at least month. closing. thank you!
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.