{"version":"2.1.323","anchor":"remote-control-reuses-the-environment-only-for-the-same-fold","canonical_anchor":"remote-control-reuses-the-environment-only-for-the-same-fold","heading":"Remote Control only reuses its environment in the same folder and machine","tier":"notice","area":"Remote Control","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/remote-control-reuses-the-environment-only-for-the-same-fold","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Remote Control only reuses its environment in the same folder and machine\n\nRemote Control now records where its environment came from and sets up a fresh one when you start it in another folder or on another machine\n\n**What**\n\nRemote Control lets you reach a Claude Code session on your computer from claude.ai. Claude Code keeps a note of the environment it registered for this, so it can reuse it. That note now also records which folder and machine it came from. If it names a different folder or machine, Claude Code registers a fresh environment instead of reusing the old one.\n\nIf registering fails, Claude Code now tries again without the old environment's ID. The warning shown when the environment does not match now adds that a project on claude.ai set to start sessions in this folder without asking will ask for your approval again.\n\n**Why**\n\nRemote Control no longer picks up an environment that belongs to another folder or machine. Expect a one-off approval prompt on claude.ai for projects that used to start without asking.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}