Repository navigation
Custom slash commands from .claude/commands/ no longer appear in autocomplete (v2.1.88) #41398
Closed as duplicate
Description
Description
After updating to Claude Code v2.1.88, custom slash commands defined in .claude/commands/*.md no longer appear in the autocomplete list when typing / in the prompt.
Steps to reproduce
- Have custom commands in
.claude/commands/(e.g.,session-save.md,daily-tasks.md) - Update Claude Code to v2.1.88
- Type
/sessin the prompt — no autocomplete suggestion appears - Previously (pre-2.1.88), typing
/sesswould showsession-savein the list
Expected behavior
Custom commands from .claude/commands/ should appear in the slash command autocomplete, as they did in previous versions.
Actual behavior
Only built-in skills (update-config, simplify, loop, schedule, etc.) appear. Custom commands from .claude/commands/ are invisible in autocomplete.
The command files are valid — correct frontmatter, UTF-8 encoding, proper permissions (644). The files haven't changed; only the Claude Code version was updated.
Environment
- Claude Code version: 2.1.88
- OS: macOS (Darwin 25.3.0, arm64)
- Node: v22.12.0
- Shell: zsh
Files in .claude/commands/
-rw-r--r-- 3489 daily-tasks.md
-rw-r--r-- 2257 rodo-check.md
-rw-r--r-- 3372 session-save.md
-rw-r--r-- 1274 start.md
-rw-r--r-- 3869 weekly-plan.md
Frontmatter example (session-save.md)
---
description: "Save session knowledge and optionally commit changes. Use before /clear, ending work, or switching context."
---
Activity
github-actions commentedon Mar 31, 2026
Found 2 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
github-actions commentedon Apr 3, 2026
This issue has been automatically closed as a duplicate of #41387.
If this is incorrect, please re-open this issue or create a new one.
🤖 Generated with Claude Code
github-actions commentedon Apr 10, 2026
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.