Follow Discord
Sweep 30 Oct 2026 · 01:02Z Build v2.1.314 532 read Stable v2.1.308 Latest v2.1.314 Next v2.1.314 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.314 ·

PreToolUse hooks can now stop project documents from reaching Claude

Each project document is checked with your PreToolUse hooks, and if a hook blocks, fails or rewrites, none of its text is sent

You'll notice Improvements
JSON All of v2.1.314
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.314,
ImprovementsSection of the release

Unclear It is not clear whether this check applies in every mode or only in certain kinds of session.

What

A hook is a command you configure that Claude Code runs at a set moment. A PreToolUse hook runs before a tool is used and can block it. Claude Code now runs your PreToolUse hooks for each project document it is about to read into the conversation.

  • If a hook fails with an error, no text from that document is sent.
  • If a hook blocks the read, no text is sent.
  • If a hook rewrites the request, no text is sent.

In each case Claude Code logs an error. Project documents are also no longer read once Claude has already replied in the conversation.

When the conversation is compacted (shortened to save space), Claude Code now asks the hooks about the project documents before it fetches any of them, and can refuse a read that a hook vetoed or whose document name does not match what was checked.

Why

Hooks can now keep project document content out of the conversation, which gives you a way to control what gets sent to the model.

Read from
Names in the bundlePreToolUse
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 not clear whether this check applies in every mode or only in certain kinds of session.

See this entry in the whole of v2.1.314 →

Feedback