What probably matters to youSection of the release
What
Slash commands now pass through a new hook chain when they run, keyed on two hook events named command.run and command.describe. A hook (a custom script that reacts to Claude Code's behavior) can observe or rewrite the text a command prints before it's shown, using a next() pattern to pass control along the chain. Claude Code also now shows a clearer error message when a queued command never actually ran, explaining that it did not go through command.run.
Why
This gives hooks a formal way to intercept and modify slash-command output, and gives users a clearer explanation when a command was queued but never executed.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed sinceAnthropic's documentation has since written up command.run, on Troubleshoot a mod.### `no command.run hook answered it`plugins/mods/troubleshootsee the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up command.run, on Troubleshoot a mod.
