[Bug] Claude Code connects to wrong IDE instance when multiple IDEs running
Resolved 💬 1 comment Opened Apr 17, 2026 by psycoder1 Closed May 27, 2026
Bug Description
When two instances of IDEs running, claude code connects to wrong instance.
Environment Info
- Platform: linux
- Terminal: pycharm <=== This is auto generated, I am not even running pycharm... I am running GoLand
- Version: 2.1.113
- Feedback ID: 0bd85b70-7510-4254-bd7f-68c3e8143773
Errors
[{"error":"Error: File does not exist. Note: your current working directory is /home/XXXXXXXX/Projects/GolandProjects/PROJECT_XXXXXXXX.\n at call (/$bunfs/root/src/entrypoints/cli.js:4734:7630)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-17T21:31:29.608Z"},{"error":"McpToolCallError: `projectPath`=`/home/XXXXXXXX/Projects/GolandProjects/PROJECT_XXXXXXXX` doesn't correspond to any open project.\n You may specify the project path via `projectPath` parameter when calling a tool. \n If you're aware of the current working directory you may pass it as `projectPath`. \n In the case when it's unobvious which project to use you have to ASK the USER about a project providing him a numbered list of the projects.\n Currently open projects: {\"projects\":[{\"path\":\"/home/XXXXXXXX/Projects/WebstormProjects/OptilmalInternalDocuments\"}]}\n at ZX7 (/$bunfs/root/src/entrypoints/cli.js:4761:63)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-17T21:47:43.858Z"},{"error":"McpToolCallError: `projectPath`=`/home/XXXXXXXX/Projects/GolandProjects/PROJECT_XXXXXXXX` doesn't correspond to any open project.\n You may specify the project path via `projectPath` parameter when calling a tool. \n If you're aware of the current working directory you may pass it as `projectPath`. \n In the case when it's unobvious which project to use you have to ASK the USER about a project providing him a numbered list of the projects.\n Currently open projects: {\"projects\":[{\"path\":\"/home/XXXXXXXX/Projects/WebstormProjects/OptilmalInternalDocuments\"}]}\n at ZX7 (/$bunfs/root/src/entrypoints/cli.js:4761:63)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-17T21:47:44.605Z"},{"error":"McpToolCallError: `projectPath`=`/home/XXXXXXXX/Projects/GolandProjects/PROJECT_XXXXXXXX` doesn't correspond to any open project.\n You may specify the project path via `projectPath` parameter when calling a tool. \n If you're aware of the current working directory you may pass it as `projectPath`. \n In the case when it's unobvious which project to use you have to ASK the USER about a project providing him a numbered list of the projects.\n Currently open projects: {\"projects\":[{\"path\":\"/home/XXXXXXXX/Projects/WebstormProjects/OptilmalInternalDocuments\"}]}\n at ZX7 (/$bunfs/root/src/entrypoints/cli.js:4761:63)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-17T21:47:45.347Z"},{"error":"McpToolCallError: `projectPath`=`/home/XXXXXXXX/Projects/GolandProjects/PROJECT_XXXXXXXX` doesn't correspond to any open project.\n You may specify the project path via `projectPath` parameter when calling a tool. \n If you're aware of the current working directory you may pass it as `projectPath`. \n In the case when it's unobvious which project to use you have to ASK the USER about a project providing him a numbered list of the projects.\n Currently open projects: {\"projects\":[{\"path\":\"/home/XXXXXXXX/Projects/WebstormProjects/OptilmalInternalDocuments\"}]}\n at ZX7 (/$bunfs/root/src/entrypoints/cli.js:4761:63)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-17T21:47:46.177Z"},{"error":"McpToolCallError: `projectPath`=`/home/XXXXXXXX/Projects/GolandProjects/PROJECT_XXXXXXXX` doesn't correspond to any open project.\n You may specify the project path via `projectPath` parameter when calling a tool. \n If you're aware of the current working directory you may pass it as `projectPath`. \n In the case when it's unobvious which project to use you have to ASK the USER about a project providing him a numbered list of the projects.\n Currently open projects: {\"projects\":[{\"path\":\"/home/XXXXXXXX/Projects/WebstormProjects/OptilmalInternalDocuments\"}]}\n at ZX7 (/$bunfs/root/src/entrypoints/cli.js:4761:63)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-17T21:47:46.635Z"},{"error":"McpToolCallError: `projectPath`=`/home/XXXXXXXX/Projects/GolandProjects/PROJECT_XXXXXXXX` doesn't correspond to any open project.\n You may specify the project path via `projectPath` parameter when calling a tool. \n If you're aware of the current working directory you may pass it as `projectPath`. \n In the case when it's unobvious which project to use you have to ASK the USER about a project providing him a numbered list of the projects.\n Currently open projects: {\"projects\":[{\"path\":\"/home/XXXXXXXX/Projects/WebstormProjects/OptilmalInternalDocuments\"}]}\n at ZX7 (/$bunfs/root/src/entrypoints/cli.js:4761:63)\n at processTicksAndRejections (native:7:39)","timestamp":"2026-04-17T21:54:05.070Z"…
Note: Content was truncated.
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗