{"version":"2.1.275","anchor":"permission-dialog-answered-away-from-the-session-is-now-reje","canonical_anchor":"permission-dialog-answered-away-from-the-session-is-now-reje","heading":"Permission dialog answered away from the session is now rejected as a denial","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/permission-dialog-answered-away-from-the-session-is-now-reje","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Permission dialog answered away from the session is now rejected as a denial\n\nAnswering a permission prompt from outside the session now counts as a denial\n\n**What**\n\nWhen a tool permission decision is set to \"ask\" and the check finds that it was `localDisplayOnly` \u2014 meaning the permission card was answered somewhere other than the active session \u2014 the tool call is now denied outright, with the message \"a permission card answered away from the session,\" instead of continuing through the normal ask-or-hook approval flow.\n\n**Why**\n\nThis closes a gap where a permission prompt answered in the wrong place could otherwise be treated as a valid approval, ensuring such cases are safely rejected.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}