Desktop app: slash command autocomplete lost after 500 error recovery

Description

Custom slash commands in .claude/commands/ stop appearing in the autocomplete dropdown after recovering from an API 500 error. The commands still execute when typed manually — only autocomplete is affected.

Steps to Reproduce

1. Open Claude Code desktop app (Mac) with a project that has .claude/commands/*.md files
2. Verify slash commands appear in autocomplete when typing / — they work fine initially
3. During a session, receive a server error: API Error: 500 The socket connection was closed unexpectedly
4. Restart Claude Code (Cmd+Q and reopen)
5. Type / — custom commands no longer appear in autocomplete

What I tried

• Quit and reopen the desktop app (multiple times)
• Full device reboot
• Verified all .claude/commands/*.md files still exist and are valid markdown
• Verified commands execute correctly when typed manually (e.g., /build-screen works)
• Confirmed the issue affects ALL commands, including ones that were not modified

Expected behavior

Custom slash commands should appear in the autocomplete dropdown after restart, just as they did before the 500 error.

Actual behavior

• Autocomplete shows skills (from .claude/skills/) but not commands (from .claude/commands/)
• Typing the full command name manually and pressing enter works — the command executes
• The issue persists across restarts and reboots

Environment

• Claude Code desktop app for Mac
• macOS Darwin 25.3.0
• Model: claude-opus-4-6 (1M context)
• 6 command files in .claude/commands/

Notes

The command files are registered internally — they appear in the skills list that Claude sees. The issue is specifically with the autocomplete UI not indexing them after crash recovery.

🤖 Generated with Claude Code