{"version":"2.1.300","anchor":"orphaned-permission-handoff-carries-turn-attribution","canonical_anchor":"orphaned-permission-handoff-carries-turn-attribution","heading":"Handed-off permission turns keep track of the turn they came from","tier":"internal","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/orphaned-permission-handoff-carries-turn-attribution","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Handed-off permission turns keep track of the turn they came from\n\nA turn handed off after an unanswered permission request now records which turn and messages it came from\n\n**Unclear.** What this changes for someone using Claude Code is not stated.\n\n**What**\n\nWhen a turn is handed off after a permission request was left unanswered, the queued turn now keeps a record of the turn and user messages it came from. That record is cleared if the handoff is converted into something else.\n\n**Why**\n\nThis keeps the conversation record consistent about which turn a handed-off request belongs to.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}