You'll noticeTier: how much it should matter to you
4Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
Remote ToolsArea: what it touches
New FeaturesKind: in v2.1.259,
What probably matters to youSection of the release
Headless or desktop cloud sessions created with permission mode auto or bypassPermissions now trigger a one-time consent dialog asking whether Claude may act unattended (auto-approving tool use). The answer is saved to unattended-serving-consent.json and shown later in settings as "Not asked yet," "Allowed," or "Not allowed." Organizations or users can preemptively turn this off with remoteTools.allowUnattendedServing: false in ~/.claude/settings.json or org policy, which surfaces the message "Turned off in your user settings (remoteTools.allowUnattendedServing: false in ~/.claude/settings.json) — remove it there to re-enable." A related, separate consent dialog asks once per computer whether a cloud session running in auto mode may run commands locally without asking each time; until answered, the cloud session keeps asking before each command.
This release deleted the gate from the code while it was still reading on for the account this site reads, so the code path no longer asks a flag before running.
This account: on · anonymous baseline: on · compiled default in v2.1.259: 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.
Gate removed from the codev2.1.259 removed the tengu_violin_fret gate from the code while it was still reading on for the account this site reads.The code path no longer asks a flag before it runs.
