Follow Discord
Sweep 06 Nov 2026 · 01:32Z Build v2.1.319 537 read Stable v2.1.311 Latest v2.1.319 Next v2.1.319 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.269 ·

"mods/" path segment resolves to a vendor claude-code-mods directory for built-in hooks modules

Built-in hooks module IDs starting with 'mods/' now resolve to a vendor claude-code-mods directory

Under the hood No documentation found Internal Changes
JSON All of v2.1.269
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Plugin HooksArea: what it touches
Internal ChangesKind: in v2.1.269,
Internal ChangesSection of the release
What

Inside the function that turns a builtin-hooks-module: identifier into an actual file path, a new rule checks whether the remainder of the identifier starts with mods/. If it does, the path resolves under vendor/claude-code-mods/mods instead of the normal built-in hooks location.

Why

This lets Claude Code load hook modules from a separate vendored claude-code-mods directory when they're referenced with a mods/ path, alongside its regular built-in hooks.

See this entry in the whole of v2.1.269 →

Feedback