{"version":"2.1.286","anchor":"ide-auto-connect-skipped-in-some-sessions","canonical_anchor":"ide-auto-connect-skipped-in-some-sessions","heading":"Automatic IDE connection is skipped in some sessions","tier":"notice","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/ide-auto-connect-skipped-in-some-sessions","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Automatic IDE connection is skipped in some sessions\n\nIn some sessions Claude Code now ignores autoConnectIde and CLAUDE_CODE_AUTO_CONNECT_IDE=true when deciding whether to connect to your editor\n\n**Unclear.** It is not clear which sessions the new check applies to.\n\n**What**\n\nClaude Code can connect automatically to your IDE (the code editor you run it inside, such as VS Code). Several things can trigger that connection. In some sessions, decided by a new check, Claude Code now skips these triggers and only connects when a connection is asked for directly:\n\n- the `autoConnectIde` setting\n\n- the `CLAUDE_CODE_SSE_PORT` environment variable\n\n- `CLAUDE_CODE_AUTO_CONNECT_IDE` set to `true`\n\nSetting `CLAUDE_CODE_AUTO_CONNECT_IDE` to `false` still turns automatic connection off, and it is still checked first.\n\n**Why**\n\nThis changes when Claude Code connects to your IDE on its own. If a session no longer connects even though you forced it with `CLAUDE_CODE_AUTO_CONNECT_IDE=true`, this check is the likely cause.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}