{"version":"2.1.293","anchor":"strict-answer-drop-telemetry-gains-context-stop-time-prompt","canonical_anchor":"strict-answer-drop-telemetry-gains-context-stop-time-prompt","heading":"More diagnostics around parked permission answers","tier":"internal","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/strict-answer-drop-telemetry-gains-context-stop-time-prompt","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### More diagnostics around parked permission answers\n\nRemote permission handling now records when a prompt ended and when a parked answer arrived, including at shutdown\n\n**What**\n\nA permission prompt is when Claude Code asks before doing something. In sessions with no one watching the screen, an answer to such a prompt can be parked, meaning held to be dealt with later. This release adds record-keeping around that.\n\n- A new `notePromptEnded(e)` records who ended a prompt and when, as `{by, atMs}`.\n\n- `onUnexpectedResponse` now calls `noteParkAnswerCameIn(e)` first, noting that a parked answer came in.\n\n- When the session shuts down while a parked permission is still waiting to be dealt with, it now calls `notePromptEnded(\"shutdown\")`.\n\n- The report sent when a strict answer is dropped now includes `parkAnswerContext` details, where before it carried only the reason.\n\n**Why**\n\nThis is diagnostic record-keeping. It gives more detail for tracking down permission prompts that get stuck in sessions with no one at the screen, and does not change how you answer prompts.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}