[Bug]: claude code builtin commands (/context, /reload-plugins, ...) do not show up in completion list

[bman654]

Before submitting

• I searched existing issues and did not find a duplicate.
• I included enough detail to reproduce or investigate the problem.

Area

apps/desktop

Steps to reproduce

1. Start a claude code session
2. type /contex or /reload-
3. look at completion list

Expected behavior

You will see /context or /reload-plugins or /reload-skills as options since those are built-in slash commands.

Actual behavior

The built-ins do not show. However if you type them correctly and hit ENTER then they execute correctly.

This used to work in Nightly a few days ago but is now broken.

Impact

Minor bug or occasional failure

Version or commit

0.0.41-nightly.20260910.1473 (b7b3ef1)

Environment

macOs

Logs or stack traces

Screenshots, recordings, or supporting files

No response

Workaround

No response

[juliusmarminge]

Thanks for the report — this looks like a real Nightly regression, and it is distinct from the older slash-command issues.

What we think is going on

T3’s / completion list is built from the last Claude capability probe, not from the live session:

• probeClaudeCapabilities in apps/server/src/provider/Layers/ClaudeProvider.ts reads initializationResult().commands
• That list is published as provider.slashCommands
• ChatComposer then offers T3 builtins (/model, /plan, /default) plus those provider commands (and skills)

T3 does not hardcode Claude builtins except /compact. A fully typed /context (or /reload-plugins / /reload-skills) is sent as ordinary prompt text to the live Claude session, so it can still execute even when it is missing from the snapshot. Composer search is unlikely to be the bug: /contex and /reload- are prefix matches and would show if those names were in the list.

Most likely the published snapshot no longer includes those Claude builtins. Two plausible sources:

1. Recent Claude CLI/SDK stopped putting host/TUI builtins in initializationResult().commands (the SDK docs still show context on system/init.slash_commands, which T3 does not merge).
2. The isolated probe (no MCP, hooks disabled, IDE skipped) no longer sees plugin-related commands that a real session still has.

The live adapter also ignores commands_changed, so a later command refresh never updates the menu.

Not a duplicate of

• [Bug]: One failed Claude capability probe empties the slash-command menu for 5 minutes and persists the empty list #7111 — one failed probe empties all provider commands and persists [] (open fix in fix(claude): keep last good slash commands after a failed probe #7175)
• [Bug]: No /compact or other slash commands available, only /model #7553 — closed; Codex-only /model
• [Bug]: Claude provider slash commands not discovered; unrecognized command freezes UI #1329 — closed; old discovery/freeze

No open PR already attributes this. The reported Nightly commit (b7b3ef1e6) is unrelated UI layout.

Next step

Confirm on current Nightly whether custom provider commands still appear (to rule out #7111), then compare the published slashCommands snapshot with Claude’s initializationResult().commands and system/init.slash_commands. If builtins are missing from init.commands, merge the system-init list (or keep a small Claude builtin fallback) and consider applying commands_changed.

Accepting as a minor bug.