Hook Source Tracking / Claude Code v2.1.75

Hooks now carry hookSource metadata indicating their origin (e.g., plugin:name, skill:name, or settings), improving debuggability.

Evidence

Hook source annotation (search for "hookSource")

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

The build it came inv2.1.75

13 Mar 2026 · 23 entries, this one is #18.

Either side of it

Open the release →

Names in this entry

cliplugin
Telemetry values now pass through marker helpers that declare them safe; nothing sent actually changed.
settingname
The SDK now rejects malformed skill names with a clear reason instead of creating a rule that never matches.
settingsettings
The runner can pass a settings file to sessions; its Windows hooks guard never actually fires.

Part of a story

This entry is one step of a feature followed across several releases. The story links it; it does not replace it.

Is this right?