Project commands from .claude/commands/ not loaded in v2.1.89
Status Fixed / completed
Maintainer reply ✓ Yes — ashwin-ant
Activity 7 comments · opened Apr 1, 2026 · closed Apr 18, 2026
💡 Likely answer: A maintainer (ashwin-ant, collaborator)
responded on this thread — see the highlighted reply below.
Description
Custom project-level slash commands from .claude/commands/ are not loaded in Claude Code v2.1.89. They don't appear in the / autocomplete list and Skill tool returns "Unknown skill" when trying to invoke them.
Steps to reproduce
- Create
.claude/commands/morning.mdwith valid frontmatter:
``yaml``
---
name: morning
description: "Morning briefing"
---
# Morning command content...
- Start a Claude Code session from the project directory
- Type
/— custom commands don't appear in the list - Try invoking via Skill tool — returns "Unknown skill: morning"
What was tried
- Adding YAML frontmatter with
nameanddescription— no effect - Creating
.claude/skills/morning/SKILL.md(plugin-style format) — no effect - Removing symlinks from commands directory — no effect
- Disabling all plugins (
enabledPlugins: {}) — no effect - Both project-level (
.claude/commands/) and global-level (~/.claude/commands/) commands are affected claude skills listCLI command DOES show the commands, but they're not available in sessions
Expected behavior
Commands from .claude/commands/*.md should appear as /command slash commands in the session, as they did in previous versions.
Environment
- Claude Code v2.1.89
- Linux (Ubuntu)
- Node.js based installation
🤖 Generated with Claude Code
7 Comments
I have the same issue. All my /commands that worked yesterday do not appear after upgrading to 2.1.89, so this problem is probably widespread
I've noticed that slash commands only search through skill/.../SKILL.md. Could you please assist in resolving this issue so they can search the entire project?
Hey, I ran into the same issue here.
Updating to the latest version (2.1.90) got the commands loading again for me.
Ref: https://code.claude.com/docs/en/changelog#2-1-90
I did check the release notes, but I didn’t see any explicit mention of a fix for this particular behavior.
Just wanted to share in case it helps anyone else hitting the same problem.
This is still happening. v2.1.87 is the last version where this was fine.
My Claude says this may share the same root cause as #41463: the bundled ripgrep binary has its execute permission stripped, causing directory scanning to fail silently. This would explain why claude skills list (different code path) sees the commands but sessions don't load them. The chmod +x fix on the ripgrep binary comes from the author of #41463. Worth trying: find "$(npm root -g)/@anthropic-ai/claude-code" -name "rg" -type f -exec ls -la {} \; — if it shows -rw-r--r-- then chmod +x that file should fix it.
This was fixed in v2.1.91 — The bundled ripgrep binary now ships with execute permissions, restoring discovery of project commands in .claude/commands/. If you're still seeing this in the latest version, please comment with your version and repro and we'll reopen.
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.