[BUG] Slash commands not loading in version 2.0.27 - "Unknown slash command" error

[jeffgehlhausen]

Preflight Checklist

• I have searched existing issues and this hasn't been reported yet
• This is a single bug report (please file separate reports for different bugs)
• I am using the latest version of Claude Code

What's Wrong?

Bug Report:

Environment

• Claude Code Version: 2.0.27
• Platform: Linux (WSL2)
• OS Version: Linux 6.6.87.1-microsoft-standard-WSL2
• Commands Directory: /home/jrg/.claude/commands/

Description

Slash commands are not being discovered or registered by Claude Code. Commands exist in the
correct directory with proper frontmatter formatting, but invoking them results in "Unknown slash
command" errors.

Additional Context

• This appears to be a regression - slash commands worked in previous versions
• The SlashCommand tool exists and is available, but command discovery/registration is failing
• Commands are never listed in available commands
• No errors shown during startup about command loading failures

Impact

Users cannot utilize custom slash commands, forcing manual copy-paste of command templates or
workarounds using MCP servers/plugins instead.

What Should Happen?

Expected Behavior

The slash commands should be recognized and executed, expanding the prompt content from the
markdown files.

Actual Behavior

Error returned:
Error: Unknown slash command: wrap-up

Error Messages/Logs

## Evidence
  Commands exist and are properly formatted:
  
  $ ls -la ~/.claude/commands/
  total 24
  drwxr-xr-x  2 jrg jrg 4096 Oct  5 09:00 .
  drwxr-xr-x 13 jrg jrg 4096 Oct 24 21:55 ..
  -rw-r--r--  1 jrg jrg 6306 Oct  5 09:00 audit.md
  -rw-r--r--  1 jrg jrg 5186 Oct  5 09:00 wrap-up.md

  Example command frontmatter from wrap-up.md:
  ---
  description: "Generate comprehensive project wrap-up documentation with findings, decisions, and     
  next steps"
  argument-hint: "[optional: specific focus like 'findings', 'technical', 'decisions',
  'next-steps']"
  ---

Steps to Reproduce

Steps to Reproduce

1. Create slash command files in ~/.claude/commands/:
   • audit.md with proper frontmatter (description, argument-hint)
   • wrap-up.md with proper frontmatter
2. Start Claude Code
3. Attempt to invoke command with /wrap-up or /audit

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.0.27

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

WSL (Windows Subsystem for Linux)

Additional Information

This happens intermittently that it stops working - perhaps with new versions - not necessarily new with this version

[github-actions]

Found 3 possible duplicate issues:

1. [BUG] Claude Code does not detect slash commands located under .claude/commands directory #9518
2. [BUG] Custom slash commands not discovered in ~/.claude/commands/ despite correct setup #8831
3. [BUG] Custom slash commands no longer working #7283

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[foglerek]

Second that I started seeing this on v2.0.27. I use project commands and they are no longer loading in new sessions. I cleared ~/.claude/projects as well to no effect.

[oswaldo]

Environment Info

• Platform: darwin
• Terminal: intellij
• Version: 2.0.28
• Feedback ID: f585d37f-9796-4ca3-b9cb-235815a6d68a

I found the same issue on v2.0.28. Symlinked commands and agents are not working anymore.
To confirm it is related to symlinks, I created a simple echo.md command like:

---
description: Simple command to test if claude code namespaced commands are working
argument-hint: give some text and the assistant should tell that back to you
---

Just echo back to the user whatever they said when calling this command

If I have this in .claude/commands, I can call /echo, if I create a subfolder t and copy it there, I can call /t:echo but if I symlink it as echolink in commands or in the subfolder, none of the expected calls work (and this symlinking strategy used to work for me until yesterday, probably before some autoupdate)

Maybe this could be related to this CVE: CVE-2025-59829: Claude Code permission deny bypass through symlink