{"version":"2.1.259","anchor":"unattended-tool-serving-requires-explicit-consent-gated-by","canonical_anchor":"unattended-tool-serving-requires-explicit-consent-gated-by","heading":"Unattended tool serving requires explicit consent, gated by a feature flag","tier":"soon","area":"Remote Tools","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259\/e\/unattended-tool-serving-requires-explicit-consent-gated-by","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259","markdown":"### Unattended tool serving requires explicit consent, gated by a feature flag\n\nA consent subsystem records whether a host may serve tool calls unattended, behind a feature flag that falls back to no on error.\n\nA new consent subsystem asks whether a host may serve tool calls unattended, persisting the answer to `unattended-serving-consent.json` and checking it before allowing unattended serving. The check runs through an async gate lookup that falls back to `false` on error, and the whole subsystem is further gated by a feature flag.\n\n- Flag `tengu_violin_fret`: Gate removed from the code (read for one account on one subscription tier against v2.1.259; this account: on, anonymous baseline: on, compiled default: no gate table built for this version) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Remote Tools\n- Names: `unattended-serving-consent.json`\n- Tier: Nothing to try yet\n- Useful: 4\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}