{"version":"2.1.321","anchor":"change-directory-tool-refuses-remote-origin-requests","canonical_anchor":"change-directory-tool-refuses-remote-origin-requests","heading":"Remote Control clients can be refused when changing a session's folder","tier":"notice","area":"Remote Control","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/change-directory-tool-refuses-remote-origin-requests","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Remote Control clients can be refused when changing a session's folder\n\nA request from a Remote Control client to change a session's working directory can be refused with the reason remote_origin\n\n**What**\n\nRemote Control lets you drive a Claude Code session from another device. A session is one running conversation with Claude Code, and its working directory is the folder it works in. A request from a remote client to change that folder can now be refused, and the session keeps its folder.\n\n- The refusal reason is `remote_origin`, added as a new failure reason for the change-directory request.\n\n- The message reads: \"This Remote Control session stays in the folder it was started in. To work in another folder, start a new session there.\"\n\n- The refusal is controlled by a server-side setting, `tengu_idempotent_blossom`. Nothing has been read about this setting, so it is not known who gets the refusal.\n\n**Why**\n\nWhere the refusal applies, you can no longer switch folders mid-session from a Remote Control client. To work in another folder, start a new session in that folder.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}