Follow Discord
Sweep 03 Nov 2026 · 22:27Z Build v2.1.318 536 read Stable v2.1.311 Latest v2.1.318 Next v2.1.318 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.318 ·

Mod hot-reload notice gains a case for mod hooks that did not load

The notice shown after a mod is reloaded can now say a mod's hooks modules did not load, and that /reload-plugins will not load them sooner

Group of 2 You'll notice Improvements
JSON All of v2.1.318
You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
PluginsArea: what it touches
ImprovementsKind: in v2.1.318,
ImprovementsSection of the release

What

Mods can be reloaded while Claude Code is running, without a restart. Afterwards Claude Code writes a notice saying what happened. The notice has changed in two ways.

  • A new case says that the mods' hooks modules did not load. Hooks are pieces of code that run automatically at set moments. The notice treats these as a person's own hooks modules, not an organization's, and says that /reload-plugins does not load them any sooner. Before, the notice only had cases for reloaded, held, unbound and failed.
  • The message for a mod that was enabled now draws on the whole reload result instead of only its load status. The wording for the declined case is unchanged: it still says /reload-plugins reloads only a mod that loaded at the start.

Why

When a mod you just wrote is not running, the notice now gives both you and Claude the actual reason: its hooks did not load. You can stop retrying /reload-plugins expecting it to fix that. The wording Claude reports after writing a mod may also change slightly.

Read from
Names in the bundle/reload-plugins

See this entry in the whole of v2.1.318 →

Feedback