{"version":"2.1.317","anchor":"headless-sessions-keep-a-persisted-tool-deny-list-across-tur","canonical_anchor":"headless-sessions-keep-a-persisted-tool-deny-list-across-tur","heading":"Headless sessions keep their blocked-tool lists between turns","tier":"internal","area":"Headless Mode","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/headless-sessions-keep-a-persisted-tool-deny-list-across-tur","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Headless sessions keep their blocked-tool lists between turns\n\nIn headless sessions, the lists of tools Claude may not use are now stored and carried across turns rather than worked out each turn\n\n**What**\n\nA headless session runs Claude Code without its interactive screen, for example from a program using the Agent SDK. The lists of tools Claude may not use used to be worked out fresh each turn. They are now stored and carried across turns, split into a list from the client and a list for the current turn. They can be restored from an earlier session's messages or saved lists.\n\n**Why**\n\nThis matters for headless sessions that are resumed, where the blocked tools can now carry over.\n\n- Area: Headless Mode\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}