A Claude Code GUI for IntelliJ IDEA That Actually Feels Native
Running an AI coding agent inside the IDE, rather than in a separate terminal, keeps the developer in the same tool where they review diffs, run tests, and debug. The SDK-based architecture also means the plugin works with cheaper third-party models, avoiding lock-in to a single provider's pricing.
CC GUI is a JetBrains plugin that brings Claude Code's agentic coding into IntelliJ IDEA without a terminal. Instead of calling the Claude CLI, it spawns a persistent Node.js daemon that loads the official Claude Agent SDK, cutting cold-start latency by 2–5 seconds per request. Communication between the Java plugin and the daemon runs over NDJSON via stdin/stdout, with request IDs enabling parallel conversations.
Configuration reuses the existing `~/.claude/settings.json`, so any model already set up in the CLI—Anthropic official, GLM-5.1, Kimi 2.6, or DeepSeek V4—works immediately. The plugin also surfaces MCP servers like Chrome DevTools for browser automation and an IDEA MCP for editor integration, plus Skill packs such as web-access and frontend-design that extend the agent's capabilities.
Two real-world refactors on an open-source community project demonstrate the workflow: migrating an article read counter from direct SQL to a Redis-backed atomic-increment scheme with batched scheduled syncs, and splitting a comment system's eager-load query into paginated top-level comments with lazy-loaded replies. In both cases, the agent scanned the codebase, proposed a multi-file plan, executed the changes, and ran browser-based verification through the Chrome DevTools MCP.
Embedding an AI agent inside the IDE changes the review dynamic: the developer can inspect every file change in real time as the agent edits, which a terminal-based agent cannot offer.
Reusing the existing Claude Code settings file is a quiet but powerful design choice—it means the plugin inherits whatever model and tool configuration the developer already trusts, with zero migration friction.
The NDJSON-over-stdin architecture is simple enough to be debuggable with basic logging, yet robust enough to support parallel agent sessions, which is rare in IDE-integrated AI tools.
Pushing browser automation through a Chrome DevTools MCP inside the IDE closes the loop between backend changes and frontend verification without leaving the editor, compressing a multi-tool workflow into one window.
Support for third-party models like DeepSeek V4 turns the plugin into a cost-control lever: a team can run the same agentic workflow at a fraction of Anthropic's API pricing without changing tools.