{"version":"2.1.260","anchor":"remote-tool-standing-approvals-capability-now-checked-and","canonical_anchor":"remote-tool-standing-approvals-capability-now-checked-and","heading":"Remote-tool \"standing approvals\" capability now checked and threaded through, source of the flag unclear","tier":"internal","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/remote-tool-standing-approvals-capability-now-checked-and","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### Remote-tool \"standing approvals\" capability now checked and threaded through, source of the flag unclear\n\nRemote tools can now advertise a standing-approvals capability that Claude Code checks for.\n\nA new `standing_approvals` capability string is checked against a remote\/MCP host's advertised description and threaded through the permission-suggestion flow as `keepsStandingApprovals`. It gates whether an accepted permission suggestion is offered as an `addRules` suggestion for remote tool calls. This is entirely host-driven, with no local flag controlling it, so it only takes effect once a remote host starts advertising `standing_approvals` in its capabilities.\n\n- Area: Permissions\n- Names: `standing_approvals`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Present in the build but not switched on"}