claude-code - 💡(How to fix) Fix Desktop app: slash command autocomplete lost after 500 error recovery [1 comments, 2 participants]

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. 3. During a session, receive a server error: API Error: 500 The socket connection was closed unexpectedly Custom slash commands should appear in the autocomplete dropdown after restart, just as they did before the 500 error.

TL;DR

The autocomplete dropdown for custom slash commands may not be updating correctly after recovering from an API 500 error, suggesting a potential caching or indexing issue.

Guidance

• Verify that the .claude/commands/ directory and its contents are correctly indexed by the Claude Code app after a restart, potentially by checking the app's internal logs or debugging output.
• Check if there are any specific error messages or warnings related to command indexing or caching in the app's logs after the 500 error occurs.
• Attempt to manually trigger a re-indexing or refresh of the autocomplete data, if such an option is available in the Claude Code app or its settings.
• Consider testing with a minimal set of command files to see if the issue persists, which could help isolate the problem.

Example

No specific code snippet is applicable in this case, as the issue appears to be related to the app's internal behavior and indexing of command files.

Notes

The issue may be specific to the Mac version of the Claude Code app or the particular environment and setup described. Further debugging or logging information may be necessary to fully diagnose and resolve the issue.

Recommendation

Apply workaround: Try manually triggering a re-indexing or refresh of the autocomplete data, or attempt to clear any cached data related to command indexing, as this may help resolve the issue temporarily until a more permanent fix is available.