Docs
EN / 中Main siteConsole
Refer friends. Keep the rewards coming!Your friend can unlock up to 10M tokens · earn up to 30% revenue share.
+500K TokensGenerate link

JetBrains Plugin

Embed CrabCode into IntelliJ IDEA / PyCharm / WebStorm / GoLand and other JetBrains IDEs.

What it is

CrabCode ships a JetBrains plugin that, together with the CrabCode CLI running in the IDE's terminal, feeds:

  • The currently open file
  • The code you have selected in the editor
  • IDE diagnostics and error markers

into the CrabCode session — so the model sees what you're looking at without you having to copy-paste.

Supported IDEs

CrabCode's JetBrains detection covers (with the matching plugin build):

  • IntelliJ IDEA (including Community / Idea Community)
  • PyCharm
  • WebStorm
  • PhpStorm
  • GoLand
  • RubyMine
  • CLion
  • Rider
  • DataGrip / DataSpell
  • AppCode
  • Aqua
  • Gateway
  • Fleet
  • Android Studio

Visual Studio Code is also supported but uses a different integration and is out of scope here.

When you see this doc

  • The /ide guide screen in the TUI
  • A status line saying "Restart JetBrains after install"
  • CrabCode detected a JetBrains terminal but no plugin

Installation

  1. IDE → Settings/Preferences → Plugins → Marketplace
  2. Search for CrabCode
  3. Install → restart the IDE when prompted

Option B: From the plugin store page

Search CrabCode on JetBrains' official plugin store and follow the "Install" link into your IDE.

IDEs from the same JetBrains SDK family usually share a plugin directory; CrabCode auto-discovers across them — you don't need to install once per IDE.

Enabling and using

After install + restart:

  1. Open the IDE's built-in Terminal and run crabcode
  2. In the session, run /ide
  3. The guide menu lists the IDE instances detected (with their workspace names)
  4. Pick one — CrabCode connects to that IDE's plugin

Once connected, the IDE's current editor selection, open file, and diagnostics feed automatically into the session.

Limits and caveats

  • CLI + plugin work together: the plugin is not standalone — it feeds context to the CrabCode CLI that you run in the IDE Terminal
  • JetBrains Gateway / remote dev: the plugin runs on the host, sees what the host CrabCode sees
  • Running CLI and plugin together: the plugin contributes context; the CLI is the session driver; memory scopes share the same ~/.crabcode/
  • Detection fails: confirm the plugin is enabled, the IDE is in the foreground, then re-run /ide to refresh