{"version":"2.1.318","anchor":"bridge-reports-missing-working-folder-when-session-spawn-fai","canonical_anchor":"bridge-reports-missing-working-folder-when-session-spawn-fai","heading":"Remote Control says when a session failed because its folder does not exist","tier":"notice","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/bridge-reports-missing-working-folder-when-session-spawn-fai","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Remote Control says when a session failed because its folder does not exist\n\nIf a Remote Control session cannot start because its working folder is missing, the error now says \"working folder not found\"\n\n**What**\n\nRemote Control lets you drive a Claude Code session on one machine from somewhere else. When starting such a session fails, Claude Code now checks whether the session's working folder exists. If it does not, the message is `working folder not found: '<dir>'` with the folder's path, instead of a general \"spawn error\".\n\n**Why**\n\nYou can see straight away that the folder is missing, rather than guessing why the session would not start.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}