{"version":"2.1.248","anchor":"permission-approvals-can-be-sent-back-with-the-tool-name-att","canonical_anchor":"permission-approvals-can-be-sent-back-with-the-tool-name-att","heading":"Permission approvals can be sent back with the tool name attached","tier":"soon","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/permission-approvals-can-be-sent-back-with-the-tool-name-att","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Permission approvals can be sent back with the tool name attached\n\nRemote permission approvals can name the tool they applied to, off in interactive sessions.\n\n**What**\n\nA new remote session option, `nameToolOnPermissionAllow`, makes an allow answer sent over the remote control channel include the name of the tool it applied to. The headless cloud client turns it on unconditionally; interactive remote sessions default it from `tengu_violin_wood`, which compiles in as false, so it is off there unless enabled server-side.\n\n**Details**\n\n- The option is new in this build.\n- Interactive sessions share the same default predicate used for keeping undelivered responses.\n\n**Evidence**\n\n`nameToolOnPermissionAllow`\n\n- Flag `tengu_violin_wood`: Off in both readings (read for one account on one subscription tier against v2.1.248; this account: off, anonymous baseline: off, compiled default: off)\n- Area: Permissions\n- Names: `nameToolOnPermissionAllow`\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}