{"version":"2.1.274","anchor":"ide-lockfile-discovery-also-checks-the-home-directory-when-c","canonical_anchor":"ide-lockfile-discovery-also-checks-the-home-directory-when-c","heading":"IDE lockfile discovery also checks the home directory when cwd is blank","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/ide-lockfile-discovery-also-checks-the-home-directory-when-c","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### IDE lockfile discovery also checks the home directory when cwd is blank\n\nIDE lockfile discovery now also checks the home directory when the working directory is blank\n\n**What**\n\nClaude Code scans certain directories to discover IDE lockfiles (used to detect a running IDE integration). That scan already included the home `.claude\/ide` directory when `CLAUDE_CONFIG_DIR` was set; it now also includes it whenever the resolved working directory is an empty string.\n\n**Why**\n\nThis closes a gap where IDE lockfile discovery could miss the home directory location in cases where no working directory was resolved, helping the IDE integration connect reliably in more situations.\n\n- Area: Elsewhere\n- Names: `CLAUDE_CONFIG_DIR`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}