Follow Discord
Sweep 27 Oct 2026 · 19:04Z Build v2.1.312 531 read Stable v2.1.308 Latest v2.1.312 Next v2.1.312 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.312 ·

Hooks in untrusted folders follow new rules

In a folder you have not trusted, Claude Code now runs only hooks defined in your own settings and no longer skips all hooks

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

Unclear It is unclear how a reader turns on the option that lets their own hooks run in untrusted folders, or whether it is on by default.

What

Hooks are commands Claude Code runs automatically at set moments. Outside the interactive screen, Claude Code used to skip every hook in a folder you had not marked as trusted. It now behaves like this:

  • Hooks that come from the folder itself still do not run. A debug line explains that the workspace is not trusted and your own settings do not define the hook.
  • Hooks defined in your own settings can run.
  • A file passed with --settings does not count as your own settings for this, so it cannot approve a hook without folder trust.

Hooks are also given the folder where the untrusted session started.

Why

The hooks that run in an untrusted folder are different now. If you rely on hooks there, define them in your own settings, not in a --settings file.

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 how a reader turns on the option that lets their own hooks run in untrusted folders, or whether it is on by default.

See this entry in the whole of v2.1.312 →

Feedback