{"version":"2.1.321","anchor":"remote-control-set-cwd-rejected-from-remote-clients-permis","canonical_anchor":"remote-control-set-cwd-rejected-from-remote-clients-permis","heading":"Remote clients can no longer change the working folder of a Remote Control session","tier":"notice","area":"Remote Control","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/remote-control-set-cwd-rejected-from-remote-clients-permis","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Remote clients can no longer change the working folder of a Remote Control session\n\nRemote Control refuses folder-change requests from remote clients, number keys skip marked options, and settings can show auto as the default mode\n\n**What**\n\nRemote Control lets you drive a Claude Code session from another device. This release makes three changes:\n\n- Changing the working folder: a request to change the session's working folder was already refused while Claude was in the middle of a turn. On a Remote Control session it is now also refused when it comes from a remote client, rather than from the program that started Claude Code and feeds it input.\n\n- Picking options with number keys: in lists of options, pressing a number now skips options that carry a marker.\n\n- Default permission mode: the settings screen now shows the default permission mode as `auto` when that is the default.\n\n**Why**\n\nA remote client now has less control over the session it is connected to. Only the program that owns the session can move it to a different folder.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}