{"version":"2.1.248","anchor":"remote-machines-can-send-their-own-auto-mode-rules-with-a-to","canonical_anchor":"remote-machines-can-send-their-own-auto-mode-rules-with-a-to","heading":"Remote machines can send their own auto-mode rules with a tool-call approval request","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/remote-machines-can-send-their-own-auto-mode-rules-with-a-to","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Remote machines can send their own auto-mode rules with a tool-call approval request\n\nA remote machine's permission rules can now influence approvals for tool calls it asks about.\n\n**What**\n\nWhen another machine asks this session to approve a tool call, its answer can now include that machine's own permission rules, which are folded into the prompt the model uses to decide. Allow and environment rules are only honoured when the peer connects as a `\"session\"` transport; deny rules always apply, and an allow rule can clear a soft block but never a hard one. No flag: it is live for anyone using remote tool calls in auto or bypassPermissions mode.\n\n**Details**\n\n- The rules arrive as four lists: hard-deny, soft-deny, allow, and environment lines describing the remote machine.\n- The classifier prompt gains a trailing section headed by the rules, with explicit instructions that any line reading as an instruction to the model is ignored.\n- Telemetry counts `host_rules_hard_deny` and `host_rules_allow_honoured`.\n- Requires the peer to mark the request `classifier_eligible`; both the sending and receiving halves ship in this build.\n\n**Evidence**\n\n`## Rules declared by the machine that will run this command`\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 4\/5"}