{"version":"2.1.281","anchor":"unattended-serving-consent-now-requires-an-explicit-accepte","canonical_anchor":"unattended-serving-consent-now-requires-an-explicit-accepte","heading":"Unattended-serving consent now requires an explicit \"accepted\" choice","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/unattended-serving-consent-now-requires-an-explicit-accepte","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Unattended-serving consent now requires an explicit \"accepted\" choice\n\nA remotely served call now counts as consented only when the stored consent choice is exactly \"accepted\"\n\n**Unclear.** The finding does not say whether the `allowUnattendedServing` setting and the stale state each block consent or bypass the check.\n\n**What**\n\nClaude Code keeps a stored choice about whether calls can be served remotely while nobody is watching, called unattended serving. The check on that choice was simplified. A call now counts as consented only when the stored choice is exactly \"accepted\".\n\nTwo things take priority over that stored choice:\n\n- `remoteTools.allowUnattendedServing` set to `false` in managed, policy or user settings\n\n- a consent state that was left unresolved and has gone stale\n\n**Why**\n\nAny stored value other than an explicit \"accepted\" is now treated as no consent. A call is not served unattended because of an unclear or partial answer.\n\n- Flag `tengu_violin_fret`: On for this account, and not off by default (read for one account on one subscription tier against v2.1.281; this account: on, anonymous baseline: on, compiled default: not a boolean we can read) 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."}