[BUG] PyCharm plugin hint from Claude Code plugin for JetBrains misleading and superfluous
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
Title: JetBrains plugin hint: misleading wording and shown even when already connected
Body:
When Claude Code is running, it displays the following hint:
▎ Install the PyCharm plugin from the JetBrains Marketplace: https://docs.claude.com/s/claude-code-jetbrains
There are two problems:
Issue 1: Misleading wording
The hint says "PyCharm plugin", but PyCharm is a JetBrains IDE, not a plugin. Users running Rider, IntelliJ IDEA, or other JetBrains IDEs may not recognise this as relevant to them. The hint
should use the actual plugin name (Claude Code [Beta]) or say "JetBrains plugin" instead.
Issue 2: Hint shown even when already connected
The hint keeps appearing even when the plugin is installed and Claude Code is actively connected to the IDE (verified via /ide). Once a connection is detected, the hint should be suppressed.
What Should Happen?
Expected behaviour:
- Use the correct plugin name / "JetBrains plugin" in the hint text.
- Do not show the hint when a JetBrains IDE connection is already active.
Error Messages/Logs
Steps to Reproduce
Install Claude Code [Beta] plugin into JetBrains Rider.
Install Claude Code
Start Claude Code from the plugin-button in Rider
Observe that claude code starts in the terminal windows, is connected with Rider but still displays the aforementioned message.
Claude Model
Sonnet (default)
Is this a regression?
No, this never worked
Last Working Version
_No response_
Claude Code Version
2.1.83
Platform
Anthropic API
Operating System
Windows
Terminal/Shell
PowerShell
Additional Information
<img width="1971" height="390" alt="Image" src="https://github.com/user-attachments/assets/c83d9f0e-8e0b-4b9b-a7a3-3e8a06639e5b" />
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗