Follow Discord
Sweep 27 Oct 2026 · 19:04Z Build v2.1.312 531 read Stable v2.1.308 Latest v2.1.312 Next v2.1.312 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.311 ·

Plugins gain a screen-refresh call and a fingerprint for their own hooks

The plugin runtime now accepts ui.invalidate, hook registration can carry a fingerprint of the plugin's hooks, and a form error reads differently

You'll notice New Features
JSON All of v2.1.311
You'll noticeTier: how much it should matter to you
4Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
PluginsArea: what it touches
New FeaturesKind: in v2.1.311,
What probably matters to youSection of the release

Unclear It is not clear whether plugins can now call ui.invalidate or whether it is only accepted as a name in a list.

What

A plugin is an add-on that extends Claude Code. A hook is code that runs when a particular event happens. Three things changed in how plugins work:

  • ui.invalidate: this is now on the list of calls the plugin runtime allows.
  • hook registration: when a plugin registers its hooks, it can now include an optional fingerprint of its own hooks file.
  • form errors: when a prompt box is left unanswered, the error now reads "the box is not answered".
Why

These changes extend what plugins can do with hooks and with Claude Code's screen.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear whether plugins can now call ui.invalidate or whether it is only accepted as a name in a list.

See this entry in the whole of v2.1.311 →

Feedback