[BUG] Windows Desktop app 1.37937 (2026-08-25 update): slash autocomplete blank, then first-position-only / single-command, chip styling gone

Still reproduces on the next Desktop build, 1.37937.1.0 — the follow-up update does not fix this.

Second machine, independent of the original report

• Desktop app: Claude_1.37937.1.0_x64__pzs8sxrjxfjjc (Store package), Windows 10 Pro 19045
• app.asar written 2026-08-26 10:58 local; every desktop claude.exe process started at 11:09, i.e. after that write — confirmed running the new build, not a stale process
• App-managed CLI: 2.1.246 (also reproduced on 2.1.241)
• Editor mode is normal — no editorMode / vimMode key present in ~/.claude.json, so this is not the vim-mode variant from #17150

Symptoms match the original report item for item: any text before / (same line or a new line) suppresses the dropdown for every command and skill; / as the first character of an empty input works; adding a second command to an input that already starts with / shows nothing.

The gate is in claude.exe, not the Electron shell

commandArgumentHint and suggestionType have 0 occurrences in the 1.37937.1.0 app.asar; that file only carries the command table (getSupportedCommands, slashCommands). Both symbols live in claude.exe. From the 2.1.246 bundle, the branch that sets suggestionType:"command":

function oS(e){
  if(!e.startsWith("/")) return !1;              // tests the WHOLE input
  let t = e.indexOf(" "),
      o = t === -1 ? e.slice(1) : e.slice(1, t); // command name assumed at index 0
  ...
}

function sve(e, t){ return !e && t.includes(" ") && !t.endsWith(" ") }

// se = full input, ke = cursor offset
if (p === "prompt" && oS(se) && ke > 0 && !sve(ot, se)) {
    ...
    suggestionType: "command"
}

Two things follow directly:

1. oS is applied to the full input string and the command name is taken with se.slice(1) — there is no cursor-relative token extraction for /. That is the "first position only" symptom.
2. sve suppresses the dropdown as soon as the input contains a space and does not end with one. That is the "only one command per message" symptom, and it also explains the clipped second-command popup in #89522.

The same module already does "sigil anywhere" — for @

let c = n.lastIndexOf("@");
if (c >= 0 && (c === 0 || xrt.test(n[c - 1]))) { ... }

So the mechanism exists in the same file and is used for at-mentions; it is simply not applied to /.

Context on earlier reports

CHANGELOG 2.1.0 documents "Added slash command autocomplete support when / appears anywhere in input, not just at the beginning", and skill stacking (/skill-a /skill-b do XYZ, up to six) is documented since v2.1.199 — so both behaviours described as "expected" here are documented, not assumed.

Earlier reports of the same thing were auto-closed without a fix and are now locked:

• #20047 — normal mode, identical repro — closed as a duplicate of #17150, which is explicitly scoped to vim mode.
• #17150, #55173 — closed by the stale bot.

Flagging that so this one does not get triaged into the same bucket.

This is just completely insane. We’re working with an AI that’s too stupid to deliver its own software without bugs. This is a massive bug. How does something like this even get approved? What the fuck are they actually programming here? I’ve had enough. We can’t work in our environment anymore. How am I supposed to remember 140 commands? And now we’ve already been waiting for two days for this to be fixed. This is a fucking joke. We can’t even downgrade because this shitty software updates itself automatically. macOS the same here !

Still reproduces on 1.37937.3, which is newer than either build reported so far (1.37937.0 original, 1.37937.1 in the comment above). Also worth noting: this machine uses the classic Squirrel installer, not the Microsoft Store package that both earlier reports used — so the regression is not specific to the Store packaging.

Environment

• Desktop app: 1.37937.3, classic install at %LOCALAPPDATA%\AnthropicClaude (Squirrel), updated 2026-08-27 03:49 local
• Windows 11 Pro, build 26200
• App-managed CLI: 2.1.246
• Separately installed npm CLI: 2.1.231 (independent of the app; the app uses its own copy)
• Skill surface: 31 personal skills plus 4 installed plugins

Symptoms — identical to the original report

• / as the first character of an empty composer: dropdown appears and filters normally.
• Any text already in the composer before the /: no dropdown at all, for every command, skill and plugin.
• Typing the full command name still executes correctly, so discovery is the only thing broken.

One data point that may narrow it down

The original report lists #48963 (the plugin path validation class) as possibly related. That looks unlikely from the shipped code: isValidPluginPath, the Skipping plugin with invalid path warning, translateInstallPath and the outside boundary check are all present and byte-identical across the app-1.34493.1, app-1.37937.1 and app-1.37937.3 bundles on this machine. Whatever changed, that validation path is not it — which points at the composer trigger condition rather than command discovery, consistent with the backend probe in the original report showing the full command list intact.