{"version":"2.1.293","anchor":"orphanedparked-permission-answers-new-telemetry-event-and","canonical_anchor":"orphanedparked-permission-answers-new-telemetry-event-and","heading":"Late permission answers in headless sessions are handled with more context","tier":"internal","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/orphanedparked-permission-answers-new-telemetry-event-and","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Late permission answers in headless sessions are handled with more context\n\nIn headless mode, permission answers that arrive after their turn now carry extra context, and closing one without running its tool is recorded\n\n**Unclear.** It is not clear what the extra context changes for you when a late permission answer arrives.\n\n**What**\n\nHeadless mode runs Claude Code without its interactive screen, for example from a script or a remote session. Sometimes a permission answer (your allow or deny for an action) arrives after the turn that asked for it has already ended. Claude Code holds such answers aside. Two things change:\n\n- Held answers now have context queued alongside them, and that context is kept when an answer is dropped.\n\n- Claude Code now records when a held permission request is closed without its tool ever running.\n\n**Why**\n\nThis is a reliability fix for remote sessions, where an answer can reach Claude Code after the turn it belongs to has moved on.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}