{"version":"2.1.290","anchor":"cloud-session-tool-host-status-banners-and-blocker-reasons","canonical_anchor":"remote-control-gains-allow-unattended-tool-calls-and-a-for","heading":"claude remote-control gains --allow-unattended-tool-calls","tier":"use","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/cloud-session-tool-host-status-banners-and-blocker-reasons","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### claude remote-control gains --allow-unattended-tool-calls\n\nA new remote-control option lets auto-mode cloud sessions run commands in your folder without asking, sandboxed, with status messages showing what is allowed\n\n**Unclear.** What decides the unattended variant's default, and whether the feature is live for any accounts, is not known.\n\n**What**\n\n`claude remote-control` connects cloud sessions to your computer. It gains a new option, `--allow-unattended-tool-calls`. With it, cloud sessions can use the current folder for one run. Commands from auto mode, where Claude decides without asking you, then run without a prompt, but only inside the sandbox. A sandbox is a walled-off area that limits what commands can touch.\n\n- It writes a grant under `~\/.claude\/state`, and exits with an error if it cannot. It says to start from your own terminal, because a sandbox cannot write there.\n\n- It starts a tool host in the foreground, unless the spawn mode is single-session. A tool host is the part that runs commands for the cloud session on this computer.\n\n- It cannot be combined with `--spawn=session`, `--session-id` or `--continue`.\n\n- It needs you at a real terminal. It refuses to start from a script, a pipe or a Claude Code session.\n\n- The setting `remoteTools.allowUnattendedServing` set to false blocks it.\n\n- New status messages cover auto mode on or off, why a folder is unavailable, and sessions starting, being refused and disconnecting. One reads: \"Your auto-mode cloud sessions can run commands on this computer without asking. Deny rules and hooks still apply. Ctrl+C to stop.\" Hooks are your own commands that run at set points.\n\n- The option's help text appears only when a condition that was not traced is met.\n\nThe unattended path is tied to the gate `tengu_violin_luthier`. Readings taken before this release found it off for this site's account and for an anonymous baseline. No reading has been taken under this release.\n\n**Why**\n\nThis is a security-relevant new ability: a cloud session can run commands on your machine without a prompt for each one. It is limited to the sandbox, deny rules and hooks still apply, and you must start it yourself at a terminal and can stop it with Ctrl+C.\n\n- Flag `tengu_violin_luthier`: Off in both readings (read for one account on one subscription tier against v2.1.290; this account: off, anonymous baseline: off, compiled default: off) 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.\n- Area: Remote Control\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}