[BUG] Project slash commands in .claude/commands/ not loaded or resolved
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?
Slash commands defined as .md files in .claude/commands/ are not discoverable or executable. They don't appear in autocomplete and don't resolve when typed in full (e.g., /ux-mockup, /commit-all).
The directory contains 28 valid .md command files, all with correct permissions (644) and valid content. Some have YAML frontmatter, some don't — neither type loads.
Plugin-provided skills (e.g from compound-engineering plugin) load and work fine. Only project-level .claude/commands/*.md files are affected.
What Should Happen?
Commands in .claude/commands/*.md should appear in autocomplete and execute
when typed as /command-name.
Error Messages/Logs
Steps to Reproduce
- Create
.claude/commands/directory in a project - Add .md files (e.g.,
commit-all.md,ux-mockup.md) - Start a Claude Code session in the project
- Type
/commit-allor/ux-mockup— command does not resolve - Check autocomplete — project commands don't appear
Claude Model
Not sure / Multiple models
Is this a regression?
Yes, this worked in a previous version
Last Working Version
v2.1.87
Claude Code Version
v2.1.89
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
- 28 .md files in
.claude/commands/ - Project also uses
compound-engineering@scoutworks-marketplaceplugin (enabled
in ~/.claude/settings.json)
- Plugin skills load correctly — only project commands fail
- Both
.claude/settings.jsonand.claude/settings.local.jsonexist — neither
contains strictPluginOnlyCustomization
- No managed settings file present
- File permissions are standard (644), owned by current us
5 Comments
I encounter the same problem after upgrading to 2.1.89 from 2.1.87.
It seems this issue has existed since version 2.1.88.
I rolled back versions as a temp fix but obviously this is a bug that needs fixing @claude
https://t.me/+t_ed3b95DqczNmU1
Closing as this seems to be fixed in v2.1.90
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.