Regression: slash command autocomplete no longer triggers mid-input (worked per v2.1.0, fixed once in v2.1.136)

Environment

• Claude Code Desktop app, Windows 10 (10.0.19045)
• claude --version: 2.1.228 (Claude Code)

Description

Slash command autocomplete only appears when / is the very first character of the input. Typing a second slash command later in the same message — e.g. /skill-a /ski — shows no suggestion menu and no highlighting for the second token. Restarting the app does not help.

Expected behavior

Per the changelog, mid-input autocomplete is a supported feature:

• v2.1.0: "Added slash command autocomplete support when \"/\" appears anywhere in input, not just at the beginning"
• v2.1.136: "Fixed mid-input slash command autocomplete not working after an initial slash command"

So the suggestion menu should appear for a / typed anywhere in the input — especially in the stacked-skill position (/skill-a /skill-b …, supported since v2.1.199), where the second name currently has to be typed blind.

Steps to reproduce

1. Open Claude Code Desktop 2.1.228, focus the chat input.
2. Type / — the autocomplete menu appears (works).
3. Complete a skill name (e.g. /my-skill), add a space, then type / followed by a prefix of another skill name.
4. No autocomplete menu appears; the second token renders as plain text.

Observed both immediately after the first slash command (stacked-skill position) and after intervening words. Reproduces consistently, including after a full app restart.