JetBrains: Ctrl+Alt+K spawns new terminal, ignores /ide-bound session
Summary
In the JetBrains plugin, the file-reference shortcut (Ctrl+Alt+K by default, which inserts @File#L1-99 into the connected Claude terminal) intermittently spawns a brand-new terminal that auto-launches claude, instead of routing the reference to the already-bound Claude Code terminal. After this happens, the original Claude terminal can no longer receive references for the rest of the session — only the spawned terminal will.
Running /ide in the original terminal (which reports Connected to PyCharm.) does not restore the binding for the next reference action — the very next Ctrl+Alt+K still spawns a new terminal.
Reproduction
- Open a project in PyCharm.
- Start
claudein the integrated terminal. - From the editor, select a few lines and press
Ctrl+Alt+K— works: reference inserted into the existing Claude terminal. - After some unidentified trigger (focus change / tab switch / time?),
Ctrl+Alt+Kinstead spawns a new PyCharm terminal that auto-runsclaude, and the reference goes to that new terminal. - In the original terminal, run
/ideand accept the listed PyCharm session to re-bind. Output:Connected to PyCharm. - Press
Ctrl+Alt+Kagain on a selection in the editor.
Expected
After step 6, the reference is routed to the original (just-rebound via /ide) terminal.
Actual
After step 6, the action still spawns yet another new terminal with claude auto-launched. The original terminal — even though /ide reported it as connected — never receives further references for the rest of the session.
Environment
- OS: Windows 11 Pro 10.0.26200
- IDE: PyCharm 2025.3.4 (Build PY-253.32098.74, built on March 24, 2026)
- Claude Code [Beta] plugin version:
0.1.14-beta(com.anthropic.code.plugin) - Custom keymap: default
Ctrl+Alt+Kremapped toCtrl+Alt+W(issue reproduces with the custom binding; not yet confirmed whether the defaultCtrl+Alt+Kreproduces it identically)
Notes
- The misroute happens with no obvious trigger — sometimes the shortcut works for many invocations in a row, then suddenly the next press spawns a new terminal.
- Once misrouted,
/idesaysConnected to PyCharm.on the original terminal but the action's target lookup still picks the spawned terminal — suggesting the reference action does not consult the/idebinding when choosing where to send the reference.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗