Follow Discord
Sweep 02 Oct 2026 · 18:55Z Build v2.1.288 509 read Stable v2.1.285 Latest v2.1.288 Next v2.1.288 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.288 ·

Plugins are read again if their settings change while hooks are being set up

If settings that affect plugins change while Claude Code is loading them, it now reads the plugins again before choosing which hooks to run

You'll notice Bug Fixes
JSON All of v2.1.288
You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
PluginsArea: what it touches
Bug FixesKind: in v2.1.288,
Bug FixesSection of the release
What

Plugins are add-ons that extend Claude Code, and some supply hooks, which are scripts that run automatically at set points during a session. Claude Code now notes the plugin-related settings in force when it starts reading your plugins. If those settings have changed by the time it picks which plugin hooks to use, it reads the plugins again first. It also reads again if it cannot work out which settings it started under.

More settings now count as plugin-affecting. Alongside enabled plugins, plugin configuration, trusted sources, marketplaces and policy settings, these now include:

Why

This stops Claude Code from picking plugin hooks based on settings that were already out of date, for example after a managed policy setting changed partway through loading.

Read from
Names in the bundledisableCommandPluginSources
What the documentation says
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 how often the extra read happens in practice or whether you would notice it.

See this entry in the whole of v2.1.288 →

Feedback