{"version":"2.1.321","anchor":"subfolder-picked-sessions-in-remote-control-bridge","canonical_anchor":"subfolder-picked-sessions-in-remote-control-bridge","heading":"Remote Control can start sessions in a folder picked on claude.ai","tier":"notice","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/subfolder-picked-sessions-in-remote-control-bridge","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Remote Control can start sessions in a folder picked on claude.ai\n\nRemote Control now accepts sessions whose folder was chosen on claude.ai, checking the folder first and refusing with a message when it cannot\n\n**Unclear.** What controls whether subfolder support is turned on was not identified, so it is unclear who can use it.\n\n**What**\n\nRemote Control lets you drive Claude Code on this computer from claude.ai. It now accepts sessions whose folder was picked on claude.ai. Claude Code checks the chosen subfolder and places the session in a worktree, a separate working copy of a git project.\n\nIt refuses to start such a session, saying it \"Didn't start session\" because its folder was picked on claude.ai, when:\n\n- subfolder support is turned off\n\n- this computer's feature flags have not loaded yet, in which case the session starts when the next message arrives in it\n\n- the path is not written in its standard full form\n\n**Why**\n\nSessions you start from claude.ai can now open in the folder you chose there, not just the default one.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}