{"version":"2.1.318","anchor":"permission-prompt-routing-stored-answer-stands-host-peer","canonical_anchor":"permission-prompt-routing-stored-answer-stands-host-peer","heading":"Permission prompts can now note that a stored answer still applies","tier":"internal","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/permission-prompt-routing-stored-answer-stands-host-peer","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Permission prompts can now note that a stored answer still applies\n\nPermission handling can record that an earlier stored answer still stands, and falls back to the session's host when finding who answered\n\n**Unclear.** It is not clear what a reader would notice differently when a stored answer is marked as still standing.\n\n**What**\n\nA permission prompt is the question Claude Code asks before it does something that needs your approval, such as running a command. Two things changed in how those prompts are routed:\n\n- When a prompt is shown, Claude Code can now record that a previously stored answer to it still stands.\n\n- When working out which connected party an answer came from, Claude Code now falls back to the session's host if it finds no other source.\n\n**Why**\n\nThis affects remote or bridged sessions, where a session is controlled from somewhere other than the terminal it runs in, and how they reuse answers you already gave.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}