{"version":"2.1.323","anchor":"plugin-reload-allow-behind-new-input-handling-in-print-mod","canonical_anchor":"plugin-reload-allow-behind-new-input-handling-in-print-mod","heading":"Headless mode changes how permission answers and plugin reloads are handled","tier":"internal","area":"Headless Mode","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/plugin-reload-allow-behind-new-input-handling-in-print-mod","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Headless mode changes how permission answers and plugin reloads are handled\n\nIn print mode with stream-json, Claude Code now counts plugin reloads and can accept a permission answer as an allow behind newer input\n\n**Unclear.** It is not stated what taking a permission answer as an allow behind new input means for which actions get approved.\n\n**What**\n\nPrint mode runs Claude Code without its interactive screen, usually driven by another program. With stream-json, that program exchanges messages with Claude Code as lines of JSON. Claude Code already kept track of permission answers and SDK server messages arriving this way, and it now also counts plugin reload requests.\n\nA permission answer can now be taken as an allow even when it arrives behind newer input.\n\n**Why**\n\nIt changes the order in which permission answers and plugin reloads from SDK or headless programs take effect.\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"}