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 ·

Empty replacement input from a permission check is now ignored

If a permission decision returns an empty set of replacement arguments for a nested tool call, the original arguments are now kept

You'll notice Bug Fixes
JSON All of v2.1.283
You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
HooksArea: what it touches
Bug FixesKind: in v2.1.283,
Bug FixesSection of the release
What

When Claude uses a tool, a permission decision, for example from a hook (a script you configure to run at set moments), can return replacement arguments for that tool. If the replacement is an empty object, {}, Claude Code now keeps the original arguments instead of using the empty one. This applies to tool calls made from inside another tool call.

Why

A hook that returns {} no longer wipes out a nested tool call's arguments.

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 doubtWhether the same fix applies to ordinary, non-nested tool calls is not known.

See this entry in the whole of v2.1.283 →

Feedback