Claude Code v2.1.300 · 14 Oct 2026
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
Use it now Tier: how much it should matter to you
5 Useful: my rating, 1 to 5
4 Signal: worth watching, 1 to 5
Plugins Area: what it touches
New Features Kind: in v2.1.300, 14 Oct 26
What probably matters to you Section of the release
What
Plugin mods can run their own code when certain events happen in Claude Code. Three things changed:
prompt.change is a new event mods can respond to.
A permission decision from a mod can now include a setting and a decider, as well as a reason, a rule and a hook. Each one must be text.
The description of the prompt-screening ability now covers the prompt.submit , command.run , session.append and session.receive hooks, plus organization policy.
Why
Mods can react to more moments and can say more about why a permission was allowed or refused.
How sure we are
One source agrees One thing we can check says the same as this entry.
Anthropic's release notes agree Added the prompt.change mod hook, raised when the prompt box's text changes without a typed edit: a recalled history entry, a clear, an…
See this entry in the whole of v2.1.300 →
14 Oct 2026 · 340 entries, this one is #11.
Use it now27 You'll notice165 Nothing to try yet4 Under the hood144
Open the release →
Names in this entry
setting prompt.change The prompt.change hook runs when a plugin or the landing screen changes the prompt box, and stops itself if plugins keep refilling it
setting prompt.submit Hooks can now rewrite or drop your prompt before it is sent.
setting command.run Plugins can now list, register, and run slash commands, and open or close a UI surface
setting append Transcript writing can be redirected to a different storage layer, but nothing turns that on here.
setting session.receive A new session.compact plugin hook can intercept and rewrite conversation compaction
Anthropic's notes
Upstream's own release notes for v2.1.300 name something this entry names, so the two are probably about the same change. Probably: the pairing is made on a shared name rather than on the words around it.
Added the prompt.change mod hook, raised when the prompt box's text changes without a typed edit: a recalled history entry, a clear, an undo, or a plugin's fill
Fixed a prompt that a mod's prompt.submit hook rewrote or dropped still being recorded as typed in the OpenTelemetry user_prompt event and interaction span, and in session title requests
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
← Previous · 10 of 340
Self-hosted runner sessions can send all traffic through a customer-run proxy
Use it now Self-Hosted Runner
In v2.1.300 What probably matters to you release-page order
Next → · 12 of 340
A new switched-off check for one tool in the arbiter permission mode
Nothing to try yet Permissions