[BUG] Slash command autocomplete doesn't filter candidates when typing after /
Resolved 💬 2 comments Opened Feb 17, 2026 by WHQ25 Closed Feb 17, 2026
Description
After typing / in the input, the slash command autocomplete menu appears correctly. However, continuing to type characters does not filter/search the command list. The menu remains showing all commands regardless of what is typed after /.
Steps to Reproduce
- Start a Claude Code session
- Type
/in the input field - The autocomplete menu appears (correct)
- Continue typing, e.g.
/comto filter for/commitor/compact - Expected: The menu filters to show only matching commands
- Actual: The menu does not filter — all commands remain visible
Environment
- Claude Code version: 2.1.44 (Homebrew cask)
- OS: macOS Darwin 25.3.0
- Terminals tested: Ghostty, Terminal.app (issue reproduced in both)
- Vim mode: Disabled
- Input method: English (no IME interference)
- Custom keybindings: Standard Autocomplete bindings (tab/escape/up/down), no conflicts
Debug Log
No [ERROR] or [WARN] entries related to slash commands or autocomplete in the session debug log. All skills and commands load successfully:
Loaded 13 unique skills (13 unconditional, 0 conditional, managed: 0, user: 8, project: 1, additional: 0, legacy commands: 4)
Plugin skills: 1, Plugin commands: 2, Bundled skills: 2
Workaround
- Use arrow keys to manually navigate to the desired command
- Type the full command name and press Enter
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗