{"version":"2.1.259","anchor":"remotetoolsallowunattendedserving-setting-formalized-in-sch","canonical_anchor":"new-settings-key-to-disable-unattended-remote-tool-serving","heading":"New setting remoteTools.allowUnattendedServing","tier":"use","area":"Remote Tools","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259\/e\/remotetoolsallowunattendedserving-setting-formalized-in-sch","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259","markdown":"### New setting `remoteTools.allowUnattendedServing`\n\nThe settings schema documents remoteTools.allowUnattendedServing, and project, local and --settings values are ignored for it.\n\nA 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.\n\n- Area: Remote Tools\n- Names: `remoteTools.allowUnattendedServing`, `--settings`\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 3\/5"}