JetBrains: Ctrl+Alt+K spawns new terminal, ignores /ide-bound session

Resolved 💬 3 comments Opened Apr 26, 2026 by bhennebel Closed Apr 30, 2026

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

  1. Open a project in PyCharm.
  2. Start claude in the integrated terminal.
  3. From the editor, select a few lines and press Ctrl+Alt+K — works: reference inserted into the existing Claude terminal.
  4. After some unidentified trigger (focus change / tab switch / time?), Ctrl+Alt+K instead spawns a new PyCharm terminal that auto-runs claude, and the reference goes to that new terminal.
  5. In the original terminal, run /ide and accept the listed PyCharm session to re-bind. Output: Connected to PyCharm.
  6. Press Ctrl+Alt+K again 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+K remapped to Ctrl+Alt+W (issue reproduces with the custom binding; not yet confirmed whether the default Ctrl+Alt+K reproduces 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, /ide says Connected 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 /ide binding when choosing where to send the reference.

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗