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.283 ·

Hooks can no longer change calls to the account memory server

Hooks may still allow or block calls to the account memory server, but a call they try to rewrite is denied and a rewritten result is dropped

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

Hooks are your own scripts or functions that Claude Code runs around its actions, for example just before a tool runs. The account memory server is an MCP server that holds memory tied to your account. An MCP server is a connector that gives Claude extra tools.

Hooks can still allow or deny a call to the account memory server, but they can no longer change it:

  • PreToolUse, PermissionRequest, managed-policy and function hooks that return changed input get the call denied and a warning logged. An empty change on the PermissionRequest path is still accepted.
  • A managed PostToolUse hook that rewrites the server's output has the rewrite dropped. The original output goes to the model.
  • A plugin hooks module that answers the call in place of the real server has its answer dropped. If the server gave no result, the call is refused.

Output rewrites for every other tool still apply.

Why

A hook defined in a repository or by a user can no longer quietly change what gets written to memory that follows your whole account.

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 stated when an account memory server is connected in the first place.

See this entry in the whole of v2.1.283 →

Feedback