{"version":"2.1.309","anchor":"remote-control-unattended-command-hint-text-rewritten","canonical_anchor":"cloud-session-messages-reworded-and-a-new-file-attach-refusa","heading":"Clearer refusal messages for cloud sessions, remote control and runners","tier":"notice","area":"Remote Control","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/remote-control-unattended-command-hint-text-rewritten","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Clearer refusal messages for cloud sessions, remote control and runners\n\nCloud and remote-control refusals are reworded, and file attachments and project_write now refuse when a repo's permission rules can't be read\n\n**What**\n\nSeveral messages you see when cloud or remote features refuse to do something have been rewritten. A cloud session is a Claude Code session that runs on Anthropic's servers instead of your own computer.\n\n- Unattended-command messages for `claude remote-control`: when commands from cloud sessions are not allowed on this computer, the message now says \"Allow them in \/config in claude, or in the Claude desktop app under Remote Control.\" It used to say \"Change that in its Claude Code settings.\"\n\n- Sandbox message: it now tells you to start `claude remote-control` again so the change is read. It used to tell you to \"run claude apply-project-settings in that folder\". A sandbox is a restricted area that limits what a command can touch.\n\n- New `repo_rules_unread` refusal for file attachments: when a cloud session cannot read the repository's permission rules, files are not attached. The message says retrying won't help and that `.claude\/settings.json` or `.claude\/settings.local.json` may need fixing.\n\n- Attachment too large: when a file is too big for a cloud environment, the error now reads `Cannot attach \"<file>\": it is larger than this session's cloud environment can attach.`\n\n- New `local_path_repo_rules_unread` error for `project_write`: `project_write` is the tool Claude uses to save project documents. When it is given a `local_path` (a file on disk to upload) and the cloud environment could not read the repository's permission rules, the file is not read and nothing is written. The message tells Claude to say that `.claude\/settings.json` or `.claude\/settings.local.json` may need fixing or removing, or to pass the text as `content` instead.\n\n- Over-1 MiB `project_write` message: it now also says nothing was written and tells Claude to tell you the file is too large to save. Before, it only said to pass the text as content.\n\n- Runner proxy-conflict error: a self-hosted runner is a machine you run that starts cloud sessions. When a runner with a `--proxy-authorization-command` \/ `--proxy-authorization-file` egress listener meets a session that uses its own proxy, the error now comes in two versions. One names the setting that points to the proxy. The other names the pool's relay mode `agent_proxy_standalone` and suggests changing the runner or the relay mode.\n\n**Why**\n\nThese are the messages you read when a remote or cloud feature refuses to run. They now point to the place where you can fix the problem, such as `\/config` or the two settings files, and tell Claude to stop and report rather than retry something that will keep failing.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: both\n- Heads-up: no"}