Follow Discord
Sweep 25 Sep 2026 · 19:33Z Build v2.1.283 504 read Stable v2.1.274 Latest v2.1.283 Next v2.1.283 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.282 ·

Hooks from settings now pass their project folder along when they run

Hooks defined in settings can now carry the project folder they belong to through to the moment they run

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

A hook is a command you configure Claude Code to run automatically at certain moments, for example before or after it uses a tool. When Claude Code gathers the hooks that apply to a moment, a hook from settings that records a project folder now keeps that folder with it until it runs. This applies only to hooks that do not already come from a plugin, a skill or another marked origin. Before, only plugin and skill information was carried along this way.

Why

In practice, a hook declared in one project's settings may now run against that project rather than whatever folder the session happens to be in.

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 unclear where the project folder gets attached to a hook, or how running the hook uses it, for example whether it sets…

See this entry in the whole of v2.1.282 →

Feedback