[BUG] Custom commands disappear from autocomplete after first use — requires CLI restart
Resolved 💬 2 comments Opened Mar 20, 2026 by rojohn10 Closed Apr 17, 2026
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?
Custom commands stored in ~/.claude/commands/ stop appearing in the / autocomplete menu after invoking any command once during a session.
What Should Happen?
Custom commands should remain in the autocomplete menu after being invoked, without requiring a CLI restart.
Error Messages/Logs
Steps to Reproduce
- Create custom commands in
~/.claude/commands/MyCommands/(e.g.,my-command.md) - Start Claude Code CLI
- Type
/— commands appear in autocomplete ✓ - Select and run a command (e.g.,
/MyCommands:my-command) - Command executes successfully ✓
- Type
/again — custom commands no longer appear in autocomplete ✗ - Typing
/MyCommandsalso shows nothing ✗ - Only way to restore: exit and restart Claude Code CLI
Claude Model
Opus
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
2.1.80
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
Terminal.app (macOS)
Additional Information
_No response_
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗