Claude Code / Platform integration
Claude Code and JetBrains
JetBrains integration is suitable for using Claude Code in environments such as IntelliJ IDEA, PyCharm, WebStorm and more.
JetBrains integration
The JetBrains plug-in brings Claude Code into IDEs such as IntelliJ IDEA, PyCharm, WebStorm and more. It's suitable for leveraging project structure, file navigation, and IDE context to complete coding tasks.
The JetBrains plug-in runs Claude Code in the IDE terminal, so many permission modes and startup parameters are consistent with the CLI. You still need to verify the modifications with real project commands.
Recommended workflow
Start the reference from the current module or file, let Claude interpret it, and give it a clear small task. Large changes should still be planned first and then implemented in stages.
locate file
Give context using the IDE project tree and the currently open file.
Let Claude plan
List the modification points and risks first.
review diff
Confirm behavior using a combination of IDE diff and test commands.
Complete usage points
Supplement the core concepts, operation sequences, permission boundaries and verification requirements that are easily compressed and missed in official documents, making it easier for English readers to learn completely by page.
JetBrains Supplement
JetBrains plug-ins are available for IDEs such as IntelliJ IDEA, PyCharm, WebStorm, etc. It lets Claude Code leverage the IDE project structure, current files, navigation, and terminal environment. Because it is typically run in an IDE terminal, many permission modes remain consistent with CLI behavior.
Suitable tasks include interpreting the current module, generating tests, fixing compilation errors, and modifying files per IDE context. For large-scale cross-module refactoring, it is still recommended to enter plan mode first and verify with real build and test commands.
Don't skip diff review just because you're in an IDE. JetBrains provides good file navigation, but the final proof of quality still comes from testing, building, and running results.
Study Checklist
Put the content on this page into real tasks and use the five dimensions of entry, context, permissions, verification and team rules to check whether you have truly mastered it.
Study Checklist
After reading this page, do not just remember the concept name. You should be able to place "Claude Code and JetBrains" back into a real Claude Code engineering workflow: where the task starts, what context the system loads, which actions need approval, how the result is verified, and how to roll back when it fails.
If this is a portal or platform page, specifically confirm what contexts this portal can access: local files, cloud repositories, browser logins, team messages, external tools, and whether these contexts are sufficient to complete the verification.
- Be able to describe in your own words the specific problem this page solves, rather than just reciting the title.
- Able to write a minimal example task with goals, scope, prohibitions, and acceptance criteria.
- Be able to determine which information should be put into the current prompt and which should be captured as project rules or configurations.
- Be able to explain which long-term rules should go into CLAUDE.md, and which runtime behavior should be handled by settings, permissions, Hooks, Skills and MCP.
- Ability to check diffs, command output, test results, screenshots or PR notes after a task is completed instead of just trusting the natural language summary.
If this page is used for team training, ask learners to complete a small task with Claude Code: read and explain first, submit a plan, make the smallest useful change, and close with real verification commands plus human diff review.