{"version":"2.1.318","anchor":"headless-withdrawn-files-and-picturestohide-handling-stops","canonical_anchor":"headless-withdrawn-files-and-picturestohide-handling-stops","heading":"New rules for which turns keep your blocked-tool list","tier":"internal","area":"Headless Mode","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/headless-withdrawn-files-and-picturestohide-handling-stops","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### New rules for which turns keep your blocked-tool list\n\nWhether a turn keeps your disallowedTools list now depends on where the message came from; headless sessions also clean up withdrawn files\n\n**What**\n\nYou 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.\n\n- 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.\n\n- 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.\n\n- `opensOnRoutineFire` is now turned off under one internal condition.\n\nIn headless mode, where Claude Code runs without the interactive screen, a few other things changed.\n\n- When files are withdrawn from a session, their entries are now removed from the record of files already read.\n\n- `picturesToHide` is passed on to the step that handles saved files.\n\n- `stopsAtToolGap` is passed from your options into each turn.\n\n**Why**\n\nThis 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.\n\n- Area: Headless Mode\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}