New rules for which turns keep your blocked-tool list

What

You can give Claude Code a list of tools it may not use, called disallowedTools. The rules for which turns keep that list have changed. A turn is one exchange of you asking and Claude answering.

• For batched messages, whether the list is kept (keepsDisallowedTools) now depends on where the message came from (inboundOrigin), whether it is a background message (isMeta), and a check on an email sender. Before, it depended on whether the turn was a task notification or had been woken up.
• The order of combining blocked-tool lists is swapped. The list sent by the client is dropped when keepsDisallowedTools is false or when the turn is carrying on. A disallowedTools list given for that one turn is always applied.
• opensOnRoutineFire is now turned off under one internal condition.

In headless mode, where Claude Code runs without the interactive screen, a few other things changed.

• When files are withdrawn from a session, their entries are now removed from the record of files already read.
• picturesToHide is passed on to the step that handles saved files.
• stopsAtToolGap is passed from your options into each turn.

Why

This changes which turns still respect tools you blocked. A queued or incoming turn may keep or drop your list depending on where its message came from, so check that tools you block stay blocked in the flows you use.