Follow Discord
Sweep 12 Nov 2026 · 23:00Z Build v2.1.323 540 read Stable v2.1.311 Latest v2.1.323 Next v2.1.323 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.323 ·

plugin validate now type-checks a plugin's TypeScript hooks module

plugin validate now checks a plugin's TypeScript hooks module for type errors and reports them as warnings for each file

Use it now Improvements
JSON All of v2.1.323
Use it nowTier: how much it should matter to you
3Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
PluginsArea: what it touches
ImprovementsKind: in v2.1.323,
What probably matters to youSection of the release
What

A plugin is a package that adds features to Claude Code. A plugin can include a hooks module, a code file that runs at set moments. plugin validate now type-checks that module when it is a TypeScript file (.ts or .tsx), meaning it looks for mistakes in how the code uses data before the code runs. The check runs in a separate process, and problems appear as warnings for each file.

  • The check is skipped, with a note, when the plugin's manifest lists dependencies.
  • When the check cannot run, for example because no suitable runtime is available, the output says the module was not type-checked.
  • A note is added when the plugin's settings.json has an agent key.
  • A plugin may only name one hooks module. If more than one is named, validation says the loader refuses both.
Why

Plugin authors writing hooks modules in TypeScript now see type errors from plugin validate before the plugin is loaded, instead of finding them later.

How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeFixed a setting saved in a running session undoing a hand edit made to settings.json moments earlier; a settings file you delete during a…

See this entry in the whole of v2.1.323 →

Feedback