{"version":"2.1.281","anchor":"ide-auto-connect-only-picks-an-ide-whose-workspace-contains","canonical_anchor":"ide-auto-connect-only-picks-an-ide-whose-workspace-contains","heading":"IDE auto-connect only attaches to an editor whose project contains your current folder","tier":"notice","area":"IDE Integration","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/ide-auto-connect-only-picks-an-ide-whose-workspace-contains","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### IDE auto-connect only attaches to an editor whose project contains your current folder\n\nClaude Code now auto-connects only to an IDE whose open workspace contains your current folder, and also lists IDEs open on a subfolder\n\n**What**\n\nClaude Code can detect a running code editor (IDE) and connect to it automatically. That now depends on which folder the editor has open.\n\n- Each detected IDE gets a new field, `workspaceContainsCwd`. It is true when the editor's open workspace contains the folder you ran Claude Code from.\n\n- Auto-connect now keeps only IDEs with `workspaceContainsCwd` and connects when exactly one is left. Before, it connected whenever exactly one IDE was found, whatever folder that IDE had open.\n\n- A new `inside-cwd` classification covers an editor whose workspace sits inside your current folder. Such an editor now counts as valid and can appear in the list, but Claude Code does not connect to it automatically. Before, an IDE counted as valid only when your folder was its workspace or sat inside it.\n\n- The handling of Windows drive letters moved into a shared helper.\n\n**Why**\n\nClaude Code no longer attaches on its own to an editor that has an unrelated project open. If you run `claude` from a parent folder of a project open in your editor, that editor can now show up in the list for you to pick.\n\n- Area: IDE Integration\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}