Skip to content

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

Description

@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

Activity

  1. added
    bugSomething is broken or behaving incorrectly.
    needs-triageIssue needs maintainer review and initial categorization.
    on Sep 10, 2026
  2. juliusmarminge commented on Sep 10, 2026

    @juliusmarminge
    Member

    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

    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.

  3. added
    acceptedfeature request accepted
    via-triageFiled through npx t3 triage
    and removed
    needs-triageIssue needs maintainer review and initial categorization.
    on Sep 10, 2026
  4. josephv123 commented on Oct 6, 2026

    @josephv123

    This no longer reproduces on current main (9503155da6) with Claude Code 2.1.290 and @anthropic-ai/claude-agent-sdk 0.3.276.

    I ran the capability probe's query options directly (never-yielding prompt, so nothing is sent). initializationResult().commands returns 69 commands, including context, reload-plugins, reload-skills and compact. The Claude provider snapshot T3 publishes from that probe lists all four as well.

    So this looks like option 1 from the triage: the CLI briefly stopped putting its builtins in init.commands, and newer CLIs put them back. T3 passes them through unchanged, so no fallback list seems needed. This can probably be closed. If someone still sees it, their claude --version would help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    acceptedfeature request acceptedbugSomething is broken or behaving incorrectly.via-triageFiled through npx t3 triage

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions