zhukunpenglinyutong/jetbrains-cc-gui

CC GUI is an IntelliJ IDEA plugin that puts a visual chat interface over command-line AI coding agents such as Claude Code and OpenAI Codex. It targets JetBrains IDE users who already (or want to) drive these CLIs but prefer in-editor conversation, diffs and file navigation to a terminal.

How it works

The plugin hosts a chat panel inside the IDE and connects to AI coding CLIs. Claude Code and OpenAI Codex are the main supported engines; Grok CLI, Kimi CLI, OpenCode, PI CLI, OMP CLI and DeepSeek Harness are listed as beta. Conversation features include @file references for sending targeted code context, image input for visual requirements, a rewind control for adjusting history, and a built-in agent system with slash commands such as /init and /review plus MCP server support. For review work, there is a code diff view and code-jump navigation; sessions can be searched, favourited and exported, with usage statistics and provider management described as cc-switch compatible.

Requirements and caveats

This is a JetBrains plugin distributed through the JetBrains Marketplace installation page, so it is not a standalone editor or a VS Code extension. The README does not state minimum IDE versions or the Node/CLI prerequisites for each engine; beta-labelled engines should be treated as less proven than Claude Code and Codex. On macOS Retina displays the README reports laggy scrolling and suggests disabling JCEF GPU acceleration through IDE VM options and restarting — a workaround with an explicit restart step.

For contributors, local development needs npm installs in both webview and ai-bridge, then Gradle tasks (runIde, buildPlugin); the packaged plugin is roughly 40 MB. The project says a /security-review audit runs before each minor release and a fuller audit every 10 minor versions — a stated process, not an independent certification.

Licence and project status

The code is MIT licensed, which permits commercial and modified use under the usual attribution terms license. The project describes itself as under active development, with change details kept in the changelog. There is no documented performance benchmark or independent comparison in the supplied material.