Command Discovery Failure: Custom Commands and Autocomplete Not Working

Resolved 💬 7 comments Opened Mar 20, 2025 by highlighter-mike Closed Aug 22, 2025

Bug Description
I am on 0.2.52 and both auto-complete and custom commands don't appear to work. But other new features do (e.g /vim and auto-accept). I've followed the instructions on creating a .claude/commands directory in my project and in my ~/ (for user scoped commands) but the commands I added as markdown files aren't available as custom commands. Typing /project: or /user: doesn't show any commands. Similarly, when I type a path into claude and press tab I do not get any autocomplete functionality.

Environment Info

  • Platform: macos
  • Terminal: Apple_Terminal
  • Version: 0.2.50
  • Feedback ID: d4d059d8-3a24-4932-9545-cf4a42eedab0

Errors

[{"error":"Error: spawn /Users/mikeoliver/Library/Application%20Support/Herd/config/nvm/versions/node/v23.1.0/lib/node_modules/@anthropic-ai/claude-code/vendor/ripgrep/arm64-darwin/rg ENOENT\n    at ChildProcess._handle.onexit (node:internal/child_process:286:19)\n    at onErrorNT (node:internal/child_process:484:16)\n    at process.processTicksAndRejections (node:internal/process/task_queues:90:21)","timestamp":"2025-03-20T17:06:05.327Z"}]

View original on GitHub ↗

This issue has 7 comments on GitHub. Read the full discussion on GitHub ↗