{"version":"2.1.286","anchor":"relay-approvals-and-permission-deny-messages-changed","canonical_anchor":"relay-approvals-and-permission-deny-messages-changed","heading":"New \"relayed\" label for approvals passed on from another session","tier":"internal","area":"Permissions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/relay-approvals-and-permission-deny-messages-changed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### New \"relayed\" label for approvals passed on from another session\n\nApprovals that arrive through a relay and are confirmed as genuine are now labelled as relayed\n\n**Unclear.** It is not known where relayed sessions are turned on.\n\n**What**\n\nWhen permission for an action comes through a relay and is confirmed as genuine, Claude Code now labels the source of the approval as \"relayed\". A relay is a session passing a message along from somewhere else. The code that builds the message for a denial made before asking was moved into a separate helper.\n\n**Why**\n\nApprovals from relayed sessions can now be told apart from other kinds of approval.\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}