Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.318 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial
Home / Reference / Settings keys

command.run

setting never mined JSON

A Claude Code settings key, read out of the shipped bundle. No mined inventory carries it: everything below comes from what this site has written about it.

Plugins can now list, register, and run slash commands, and open or close a UI surface

Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.265.

First seen — never in a mined build
Last seen — never in a mined build
Builds0 / 159on this box, as of v2.1.319
Written about v2.1.265 first named in a changelog, 8 Sep 2026

In the changelogs

23

Releases whose published page names command.run.

  1. v2.1.304
    Plugin mods are now checked for a screen-drawing hook

    Claude Code now looks for a ui.render hook in plugin mods, and drafts written into the input box can carry decorations

    found in this entry's text

  2. v2.1.300
    Plugin mods gain a prompt-change event and richer permission decisions

    Plugin mods get a prompt.change event, and permission decisions can now name a setting and a decider

    found in this entry's text

  3. v2.1.292
    Plugins can hook into prompt autocomplete

    Plugins gain a prompt.autocomplete hook point, and the plugin checker lists hooks that answer a plugin's own command separately

    found in this entry's text

  4. v2.1.292
    Plugin tests report failures, and the code scan checks more

    Closing a plugin test now reports whether it failed, and the plugin code scan catches redeclared names and the plugin's own commands

    found in this entry's text

  5. v2.1.292
    A prompt-cache log message is reworded and two internal labels change

    A log message about the prompt-cache relay has new wording, and two internal command labels were added or annotated

    found in this entry's text

  6. v2.1.286
    Plugin test scans cover SubagentStop hooks, MCP connections and toasts

    The plugin test scan list now includes the SubagentStop hook and calls to connect to MCP servers and show toasts, and drops two calls

    found in this entry's text

  7. v2.1.283
    Plugin command hooks now receive only the commands they match

    Plugin hooks on the command.run event can list the commands they want and only receive those

    found in this entry's text

  8. v2.1.275
    Plugin-originated slash actions now include prompt.fill and prompt.suggest, not just command.run

    Plugin-triggered slash actions now also cover prompt.fill and prompt.suggest, not just command.run

    found in this entry's text

  9. v2.1.275
    Skill/command execution now restricted to composer or bridge message origins

    Skills and slash commands now only run when triggered from the composer or a bridge message

    found in this entry's text

  10. v2.1.275
    plugin.command.run character-limit check silently removed

    Plugin command.run no longer rejects overly long arguments, only logs their length

    found in this entry's text, named in this entry

  11. v2.1.271
    Plugin command.run now threads an origin/rootEvent chain

    Plugin commands now record where they came from and their root event when dispatched

    found in this entry's text

  12. v2.1.271
    Plugin command.run replay now pins the answer's presentation location

    Plugin command.run replay now refuses to replay if the answer's display location changed

    found in this entry's text

  13. v2.1.269
    prompt.submit error now points to command.run

    The prompt.submit plugin API error now tells you to use command.run instead

    found in this entry's text

  14. v2.1.269
    New tool/config SDK operations pass through unmodified

    SDK gains tool.check, config.set, and config.describe pass-through operations

    found in this entry's text

  15. v2.1.265
    New plugin host APIs: command.list, command.register, command.run, ui.open, ui.close

    Plugins can now list, register, and run slash commands, and open or close a UI surface

    found in this entry's text, named in this entry

  16. v2.1.265
    Plugin SDK gains a command namespace: register/run/list slash commands

    Plugins can now register, run, and list slash commands through a new $.command API

    named in this entry

  17. v2.1.265
    Plugin commands can now be registered/run/described via new $.command.* hook API

    Plugins can now register, run, list and describe their own slash commands via a new command API

    found in this entry's text

  18. v2.1.265
    Command execution can now be intercepted by command.run/command.describe hooks

    Slash-command execution can now be intercepted and rewritten by command.run/command.describe hooks

    found in this entry's text, named in this entry

  19. v2.1.265
    New 'command.run' hook pipeline for slash-command dispatch

    Slash commands can now be intercepted and their output overridden by a new 'command.run' hook

    found in this entry's text, named in this entry

  20. v2.1.265
    Functionhooks event registry expands: ui.open/ui.close, command.run/command.describe, classic.PreToolUse

    Hooks system adds ui.open/ui.close and command.run/command.describe event types, and renames PreToolUse internally

    found in this entry's text, named in this entry

  21. v2.1.265
    Plugin runtime API gains command hooks and UI window controls

    Plugins can now register and run their own commands and open or close their own UI windows

    found in this entry's text

  22. v2.1.265
    Plugin telemetry site map gains command.run and command.describe hooks

    Plugin hook telemetry adds command.run and command.describe event types

    found in this entry's text

  23. v2.1.265
    Hook events: PreToolUse split into classic vs. new, and two new synchronous hook events added

    PreToolUse hooks are now split into a classic and new form, plus two new synchronous hook events

    found in this entry's text, named in this entry

First cited

5

The earliest release whose published evidence quoted command.run was v2.1.265, 8 Sep 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.

ReleaseDateThe span that was quoted
v2.1.2658 Sep 2026"command.run": Byo,
v2.1.2658 Sep 2026"command.run": Pi,
v2.1.2658 Sep 2026add on("command.run", { command: "${n.name}" }, ($, e) => ({ text: ... })) to the plugin.
v2.1.2658 Sep 2026the command did not go through command.run
v2.1.27517 Sep 2026_Ce(r.plugin, "command.run", (n.args ?? "").length);

Presence across releases

0

The miner has never read a build containing this name. It is here because a changelog entry of ours names it, which is evidence that it existed and not evidence of which releases carried it. The inventory starts at v2.1.138 and everything older than that was never mined.

Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the settings key does. All settings keys.

Feedback