CC GUI tackles a common frustration developers face when juggling AI coding assistants that run primarily as command-line tools. Instead of switching context between terminal and IDE, CC GUI embeds Claude Code and OpenAI Codex directly into JetBrains IDEs like IntelliJ IDEA. This native integration smooths out the developer workflow by bringing AI assistance where code is actually written.
What CC GUI does and how it works
At its core, CC GUI is a TypeScript-based plugin for JetBrains IDEs that wraps two major AI engines—Claude Code and OpenAI Codex—into a unified, native IDE interface. The plugin architecture follows the standard Gradle-based JetBrains plugin model, combining a webview-based frontend with an ai-bridge backend written in TypeScript.
The plugin supports dual AI engines, allowing users to switch between Claude Code and Codex smoothly, catering to different AI capabilities or preferences. It also integrates with the Model Context Protocol (MCP) server, which helps synchronize context and session state, a feature crucial for maintaining coherent AI conversations across multiple sessions.
One of the standout features is the agent system with slash commands. This system enables users to invoke specialized AI commands directly within the IDE, extending the assistant’s capabilities in a structured way. The plugin also respects IDE permission models, ensuring that AI access to code or resources is carefully controlled.
From a user experience perspective, CC GUI synchronizes with the IDE’s font and theme settings, making the AI interface feel native and consistent with the developer’s environment. It also offers code diff viewing for AI-generated changes, allowing developers to review suggestions side-by-side before accepting them.
The package size is approximately 40MB, which reflects the complexity of embedding multiple AI engines and a rich frontend UI inside the plugin.
What sets CC GUI apart technically
What distinguishes CC GUI is its deep embedding of AI assistants within the JetBrains ecosystem rather than relying on external CLI tools or standalone apps. This reduces the friction of context-switching and enables a workflow where AI assistance feels like a natural part of the IDE.
The dual AI engine support is a clear strength. Many AI coding tools lock you into one provider; CC GUI’s approach lets you pick Claude Code or Codex depending on your needs or preferences. Under the hood, managing two different AI backends and synchronizing context with MCP is no small feat. It requires careful session management and secure communication channels.
The agent system with slash commands introduces a modular way to extend AI capabilities, which is a sophisticated approach compared to basic chat interactions. This design allows for more structured and reusable AI commands, potentially improving productivity.
On the backend, the ai-bridge written in TypeScript mediates communication between the webview UI and the AI engines. This separation aligns well with JetBrains plugin architecture but adds complexity in maintaining synchronization and responsiveness.
Security is taken seriously, with audits before minor releases, an important consideration given the sensitive nature of code access in AI tools.
The tradeoff here is between a heavier plugin footprint (~40MB) and the improved developer experience from native integration. Lightweight CLI tools are easier to install and have smaller footprints, but they don’t offer the same seamlessness or security controls.
Explore the project
The repository contains the plugin source coded primarily in TypeScript, organized around the JetBrains Gradle plugin structure. The core components are:
- Frontend: A webview interface that renders the AI assistant UI inside the IDE.
- Backend (ai-bridge): Handles communication with Claude Code and Codex AI engines, manages session state, and integrates MCP protocol support.
- Agent system: Implements slash commands and specialized AI interactions.
The README provides a high-level overview of features and architecture but does not include explicit installation commands or quickstart scripts.
For developers interested in contributing or exploring, the best entry point is the README and code organization around the Gradle plugin setup. Understanding JetBrains plugin development and the MCP protocol will be essential to grasp the full scope.
The plugin also uses IDE font and theme synchronization, so exploring how it hooks into JetBrains platform APIs for UI consistency is worth attention.
Verdict
CC GUI is a solid tool for JetBrains users who want AI coding assistants integrated directly into their IDE without leaving the editor or managing multiple CLI tools. Its dual AI engine support, agent system, and session management features provide a richer AI coding experience.
The tradeoff is a larger plugin size and the complexity of maintaining deep IDE integration, which may not suit lightweight or minimal setups. Also, it depends on JetBrains IDEs, so users outside that ecosystem won’t benefit.
For developers or teams invested in JetBrains tools and looking to incorporate AI assistance more seamlessly into their workflow, CC GUI is worth exploring. It addresses a real pain point of context-switching and permission management that many AI coding CLI tools overlook.
The project’s mature approach, including security audits and careful architecture, suggests it could be a dependable component of an AI-augmented coding environment. That said, if you prefer minimalism or use multiple IDEs, you might find the footprint and IDE-specific constraints limiting.
Related Articles
- CC Switch: unified management for AI coding CLIs in a cross-platform Rust desktop app — CC Switch is a Rust-based cross-platform desktop app that centralizes management of AI coding CLIs like Claude Code and
- OpenAI Codex CLI: local-first AI coding assistant with ChatGPT integration — OpenAI Codex CLI brings AI coding assistance local to your terminal, integrating with ChatGPT plans for powerful hybrid
→ GitHub Repo: zhukunpenglinyutong/jetbrains-cc-gui ⭐ 3,185 · TypeScript