What probably matters to youSection of the release
A new managed/user settings key remoteTools.allowUnattendedServing (settable in ~/.claude/settings.json at the org or user level) controls whether unattended remote-tool serving is allowed. When set to false, a cloud session in auto mode cannot run commands on the local computer without per-command approval; project/local/--settings values are ignored for this key. Invalid values fall back to allowUnattendedServing: !1 (false, i.e. no unattended serving), and the key is registered as non-restrictive in the settings policy list. The UI surfaces a specific explanation depending on whether it was turned off by the organization's settings ("Turned off by your organization's settings (remoteTools.allowUnattendedServing)") or the user's own settings.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added sinceA small documentation edit on Week 20 · May 11–15, 2026 touched a line naming --settings after this was published.<div><code>claude agents</code> gained dispatch flags (`--add-dir`, `--settings`, `--mcp-config`, `--plugin-dir`, `--permission-mode`, `--model`, `--effort`, `--dangerously-skip-permissions`) to configure background sessions, and `claude a…whats-new/2026-w20see the edit
Confirmed sinceAnthropic's documentation has since written up --settings, on CLI reference.| `claude agents` | Open [agent view](/docs/en/agent-view) to monitor and dispatch parallel background sessions. Use `--cwd <path>` to show only sessions started under that directory, or `--json` to print active sessions as a JSON array fo…cli-referencesee the edit
How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agreesAnthropic's documentation has since written up --settings, on CLI reference.
