Claude Code v2.1.265 · 8 Sep 2026
Hook registry gains command.describe as a core hook event
Claude Code adds a new internal hook event called command.describe
Under the hood Tier: how much it should matter to you
2 Useful: my rating, 1 to 5
2 Signal: worth watching, 1 to 5
Hooks Area: what it touches
Internal Changes Kind: in v2.1.265, 08 Sep 26
Internal Changes Section of the release
Unclear What functionality actually uses the new command.describe hook is not established by this finding.
Why
This is internal plumbing rather than something a reader interacts with directly. It suggests Claude Code now has a defined point for describing commands, similar to how it already describes tools, but the finding doesn't say what consumes this event yet.
What the documentation says
How sure we are
Something disagrees Something we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt What functionality actually uses the new command.describe hook is not established by this finding.
See this entry in the whole of v2.1.265 →
8 Sep 2026 · 371 entries, this one is #299.
Use it now40 You'll notice132 Nothing to try yet30 Under the hood169
Open the release →
Names in this entry
setting command.describe Plugins can now register, run, list and describe their own slash commands via a new command API
setting agent Start every session as a named subagent with its prompt, tools, and model
setting session.start Two hook events arrive: session.start fires on terminal session start, and prompt.context is registered but has no emitter here.
setting turn.start Plugin hooks are limited in what they may rewrite, and cannot take over question prompts.
setting turn.step Plugin hooks are limited in what they may rewrite, and cannot take over question prompts.
setting turn.complete Plugin hooks are limited in what they may rewrite, and cannot take over question prompts.
Is this right?
0
0
Feedback
What's wrong with this entry?
Hard to understand Too vague Looks wrong Not relevant to me Too long Missing the detail I wanted Duplicate of another card
Clear Learned something new I can act on this Good catch
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
← Previous · 298 of 371
Hook events: PreToolUse split into classic vs. new, and two new synchronous hook events…
Under the hood Hooks
In v2.1.265 Internal Changes release-page order
Next → · 300 of 371
Permission-check pipeline gained a pre-hook adjustment step (uot) before deny/ask…
Under the hood Hooks