{"version":"2.1.290","anchor":"unattended-serving-consent-check-now-takes-a-per-call-argume","canonical_anchor":"unattended-serving-consent-check-now-takes-a-per-call-argume","heading":"Consent for unattended calls can now be decided per call","tier":"internal","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/unattended-serving-consent-check-now-takes-a-per-call-argume","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Consent for unattended calls can now be decided per call\n\nThe consent check for unattended calls now also looks up consent for each call or target, not only one global setting\n\n**Unclear.** What the new per-call lookup checks, and which feature uses this path, is not known.\n\n**What**\n\nClaude Code checks whether you have consented before making certain calls when nobody is at the keyboard. This check used to treat a call as unconsented when there was no consent value or when the settings were out of date. It now also does a further lookup for each call, using information passed in from the part of Claude Code that reports consent states such as `consent_forced_off`, `consent_declined` and `consent_unset`. If reading consent fails, the call is still treated as unconsented.\n\n**Why**\n\nThis changes when unattended or automatic calls count as consented: consent can now differ from one call or target to another.\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}