Custom slash commands not appearing in autocomplete (Claude Code 1.0.83)

Status Fixed / completed
Maintainer reply ✓ Yes — ant-kurt
Activity 9 comments · opened Aug 17, 2025 · closed Aug 19, 2025
💡 Likely answer: A maintainer (ant-kurt, collaborator) responded on this thread — see the highlighted reply below.

Description:
Custom slash commands are not appearing when typing "/" despite proper configuration and multiple restarts.

( *Note this is what Claude Code told me to tell you, we tried to resolve after 10 or so attempts, here we are)

Environment:

  • Claude Code version: 1.0.83
  • Platform: macOS (Darwin 24.6.0)
  • Commands location: /Users/webdev/.claude/commands/

Configuration:
// .claude/settings.json
{}

// .claude/settings.local.json
{
"permissions": {
"allow": [...],
"deny": [],
"additionalDirectories": ["/Users/webdev/.claude/commands"]
}
}

Command files:

  • /Users/webdev/.claude/commands/gitcomment.md (522 bytes)
  • /Users/webdev/.claude/commands/invoice-notes.md (2915 bytes)
  • Files have 644 permissions
  • Proper markdown format with # Command Name headers

Expected behavior: Typing "/" should show /gitcomment and /invoice-notes in autocomplete

Actual behavior: No custom commands appear in autocomplete

Troubleshooting attempted:

  • Multiple Claude Code restarts
  • Recreated command files from scratch
  • Tested both relative and absolute paths
  • Cleared configuration conflicts
  • Verified file permissions and format

Question: Do built-in commands (like /help) appear when typing "/"?

View original on GitHub ↗

9 Comments

github-actions[bot] · 1 year ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/2288
  2. https://github.com/anthropics/claude-code/issues/573
  3. https://github.com/anthropics/claude-code/issues/1416

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

michaelgrafwebdev · 1 year ago

dup

ant-kurt collaborator · 1 year ago

We shipped some improvements in 1.0.84 that should help diagnose / mitigate this:

  1. claude /doctor now shows the status of Search related functionality (which includes custom slash command discovery)
  2. Claude Code now prefers built-in rg over system-installed rg (see https://docs.anthropic.com/en/docs/claude-code/troubleshooting#search-and-discovery-issues)
  3. You can also run with --debug to see if there are rg related errors
clouedoc · 1 year ago

I am on Fedora Asahi Linux Remix 42
Somehow the ripgrep that you're shipping was not working.
I added the env var like so in my zshrc:

alias claude="USE_BUILTIN_RIPGREP=0 /home/clouedoc/.claude/local/claude"

Seems to be working now.

ant-kurt collaborator · 1 year ago

Glad you have a workaround - @clouedoc are you using the npm-based installation or the native installer?

clouedoc · 1 year ago
Glad you have a workaround - @clouedoc are you using the npm-based installation or the native installer?

No idea, sorry :-)

ant-kurt collaborator · 1 year ago

claude /doctor will tell you - if path / invoked is node and claude, that's npm-based. Otherwise if it's just a Claude executable under a path like .local/bin/claude, then it's native.

Asking because ripgrep we're shipping really should work in the npm-based flow, but we have some known issues with native.

clouedoc · 1 year ago
> /doctor 

 Diagnostics
 └ Currently running: npm-local (1.0.95)
 └ Path: /usr/bin/node-22
 └ Invoked: /home/clouedoc/.claude/local/node_modules/.bin/claude
 └ Config install method: local
 └ Auto-updates enabled: true
 └ Search: OK (/usr/bin/rg)
 Warning: Multiple installations found
 └ npm-local at /home/clouedoc/.claude/local
 └ npm-global at /usr/local/bin/claude
 Warning: Local installation not accessible
 Fix: Alias exists but points to invalid target: USE_BUILTIN_RIPGREP=0. Update alias: alias claude="~/.claude/local/claude"
github-actions[bot] · 1 year ago

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.