[BUG] Slash command autocomplete: filtering stuck, wrong command executes, crash on mid-sentence / (v2.1.41)

Status Closed — duplicate
Maintainer reply None cached
Activity 3 comments · opened Feb 13, 2026 · closed Feb 16, 2026

Description

Three related slash command autocomplete bugs, all reproducible on v2.1.41. These appear to be regressions or continuations of issues reported in earlier versions.

Bug 1: Autocomplete filtering doesn't follow typed input

When typing a slash command, the autocomplete stays stuck on the first alphabetical command instead of filtering to matching commands.

Steps to reproduce:

  1. Open Claude Code CLI
  2. Type / — autocomplete highlights the first command alphabetically (correct)
  3. Continue typing to narrow down (e.g., /hel to reach /help)
  4. Autocomplete remains stuck on the first command instead of filtering

Bug 2: Wrong command executes regardless of selection

Even when using arrow keys to navigate to a different command, pressing Enter still executes the first command in the list.

Steps to reproduce:

  1. Type / to open autocomplete
  2. Use arrow keys to navigate to a different command
  3. Press Enter
  4. The first alphabetical command executes instead of the highlighted one

Bug 3: Crash when typing /{anything} mid-sentence

Typing a forward slash followed by any text in the middle of a sentence causes a crash with:

ERROR (H.description??"").split is not a function.
(In '(H.description??"").split(" ")', '(H.description??"").split' is undefined)

Stack trace:

- <anonymous> (/$bunfs/root/claude:7366:12463)
- map (native:1:11)
- EdA (/$bunfs/root/claude:7366:12343)
- hdA (/$bunfs/root/claude:7366:10547)
- <anonymous> (/$bunfs/root/claude:7367:5646)
- hC (/$bunfs/root/claude:682:29832)
- <anonymous> (/$bunfs/root/claude:177:273010)
- T80 (/$bunfs/root/claude:7367:5574)
- fv8 (/$bunfs/root/claude:7403:5684)
- KD (/$bunfs/root/claude:682:20803)

Root cause: EdA (slash command fuzzy search) → hdA (inline ghost text) calls .split(" ") on a description field that is not a string. The nullish coalescing ?? "" doesn't catch it because the value exists but is not a string type (likely an object from a skill/command metadata).

Environment

  • Claude Code Version: v2.1.41
  • Model: Opus 4.6 (Claude Max)
  • Platform: macOS Darwin 25.3.0
  • Installation Method: Native
  • Skills installed: 50+ custom skills (global + plugin)

Related Open Issues

  • #19107 — Autocomplete always selects wrong command (v2.1.12)
  • #18898 — Highlighted command doesn't match typing, Enter runs wrong command (v2.1.12)
  • #17853 — description.split TypeError crash on every keystroke (v2.1.6)
  • #18117 — $.description.split is not a function crash (macOS)
  • #21924 — Malformed YAML in skill description breaks autocomplete (v2.1.25)

Filing this to confirm all three bugs persist in v2.1.41 with the additional mid-sentence crash variant and detailed stack trace.

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗