[Bug] Custom slash command appears duplicated and incorrectly highlighted in command selection menu

Status Fixed / completed
Maintainer reply None cached
Activity 8 comments · opened Nov 4, 2025 · closed Nov 15, 2025

Bug Description
i have defined my custom slash command in user-wide setup and name it commit.md. but now everytime i type slash to do anything the custom command always shows up in the first order and often be in active state as if i am selecting it (in blue color text). even when i type for unrelated slash like i type "/usage" the /commit commands shows up twice like this

/commit Analyze changes and create atomic commits by logical unit, not by file. Use type: message format ... (project)
/usage Show plan usage limits and both the commit slash is in blue color which confuse me. but then if  i press enter the usage slash is the one selected tho
/commit Analyze changes and create atomic commits by logical unit, not by file. Use type: message format ... (project)

Environment Info

  • Platform: darwin
  • Terminal: cursor
  • Version: 2.0.32
  • Feedback ID: 8ba03507-ae71-4925-b6c7-63f66b930cce

Errors

[{"error":"Error: 1: 1 \n    at xID (/$bunfs/root/claude:513:3997)\n    at async MID (/$bunfs/root/claude:513:1612)\n    at processTicksAndRejections (native:7:39)","timestamp":"2025-11-03T23:58:56.439Z"},{"error":"Error: Language not supported while highlighting code, falling back to markdown: vue\n    at Fq (/$bunfs/root/claude:1210:3185)\n    at map (native:1:11)\n    at k3 (/$bunfs/root/claude:1210:2902)\n    at IOB (/$bunfs/root/claude:1749:17060)\n    at tZ (/$bunfs/root/claude:101:19415)\n    at gn (/$bunfs/root/claude:103:42816)\n    at h1 (/$bunfs/root/claude:103:38357)\n    at Kd (/$bunfs/root/claude:103:38285)\n    at WE (/$bunfs/root/claude:103:38139)\n    at sQ (/$bunfs/root/claude:103:35218)","timestamp":"2025-11-04T00:00:04.881Z"},{"error":"Error: Language not supported while highlighting code, falling back to markdown: \n    at Fq (/$bunfs/root/claude:1210:3185)\n    at map (native:1:11)\n    at k3 (/$bunfs/root/claude:1210:2902)\n    at nQB (/$bunfs/root/claude:1730:6593)\n    at tZ (/$bunfs/root/claude:101:19415)\n    at gn (/$bunfs/root/claude:103:42816)\n    at h1 (/$bunfs/root/claude:103:38357)\n    at Kd (/$bunfs/root/claude:103:38285)\n    at WE (/$bunfs/root/claude:103:38139)\n    at sQ (/$bunfs/root/claude:103:35218)","timestamp":"2025-11-04T00:00:17.893Z"}]

<img width="622" height="129" alt="Image" src="https://github.com/user-attachments/assets/e43b3922-7044-4041-85a2-46f645596965" />

View original on GitHub ↗

8 Comments

github-actions[bot] · 9 months ago

Found 1 possible duplicate issue:

  1. https://github.com/anthropics/claude-code/issues/10383

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

ollieatkinson · 9 months ago

I am also seeing this

<img width="678" height="682" alt="Image" src="https://github.com/user-attachments/assets/787ac25e-101f-44d7-8a5b-5d12a1357775" />

IrumiDesu7 · 9 months ago
I am also seeing this

that's a lot of duplication going on. mine only duplicate into 2 sometimes 3 commands

ollieatkinson · 9 months ago

You can easily reproduce it by navigating the menu

Zirkus-99 · 9 months ago

Do you guys have a header in your ~/.claude/commands/command-a.md?

---
description: a custom slash command
---

After I removed the header, it looks like:

/command-a a custom slash command(project, gitignored)

And the scroll works well.

IrumiDesu7 · 9 months ago
Do you guys have a header in your ~/.claude/commands/command-a.md? --- description: a custom slash command --- After I removed the header, it looks like: /command-a a custom slash command(project, gitignored) And the scroll works well.

i don't have it in the first place

IrumiDesu7 · 9 months ago

as of v2.0.42 this bug is now solved

github-actions[bot] · 9 months ago

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.