{"version":"2.1.248","anchor":"session-decides-for-itself-whether-remote-rules-may-influenc","canonical_anchor":"session-decides-for-itself-whether-remote-rules-may-influenc","heading":"Session decides for itself whether remote rules may influence approval","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/session-decides-for-itself-whether-remote-rules-may-influenc","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Session decides for itself whether remote rules may influence approval\n\nA remote host's permission rules only count when you're in auto mode and the tool isn't ask-first.\n\n**What**\n\nOn receiving a `needs_approval` answer from a remote host, the session checks its own permission mode before letting the host's rules count. The host's allow, soft-deny, hard-deny and environment lines are forwarded to the decision prompt only when the local mode is `auto`, the host marked the call eligible, and the tool is not in ask-first mode.\n\n**Details**\n\n- Each forwarded rule line is trimmed and empty entries dropped.\n- An approval made by the automatic classifier rather than a person is now tracked as such and carried into the recovery path for dropped or timed-out calls.\n\n**Evidence**\n\n`classifierEligible: nn,`\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 4\/5"}