A Claude Code IDE integrationis a plugin or extension that embeds Claude's AI coding capabilities directly into your preferred development environment. Instead of switching between your editor and a separate terminal window, IDE integrations bring Claude into your existing workflow through sidebar panels, inline suggestions, context menus, and keyboard shortcuts. The result is a seamless development experience where AI assistance is always one keystroke away.
VS Codeis the most popular editor for Claude Code users, and its integration is the most feature-rich. The VS Code extension provides a dedicated sidebar panel where you can chat with Claude about your current file, selected code, or entire workspace. Claude understands your project structure, open files, and recent edits, providing contextually relevant suggestions without requiring you to manually describe your codebase. The extension also supports inline code suggestions that appear as ghost text as you type, similar to traditional code completion but powered by Claude's deep understanding of your project.
JetBrains IDE integrationsbring Claude Code to IntelliJ IDEA, WebStorm, PyCharm, GoLand, RubyMine, PhpStorm, and every other JetBrains product. The JetBrains plugin integrates with the platform's native inspection system, allowing Claude-powered code analysis to appear alongside standard IDE warnings and suggestions. Developers can invoke Claude through intention actions (the familiar Alt+Enter menu), use it in the refactoring workflow, and access it from the built-in terminal. The plugin respects JetBrains project structures including module boundaries, run configurations, and version control settings.
Neovim integrations cater to developers who prefer a keyboard-driven, modal editing experience. Community-built Lua plugins like claudecode.nvimprovide native Neovim integration with features including split-pane Claude sessions, visual selection context passing (select code and send it to Claude with a keybinding), telescope integration for navigating Claude suggestions, and buffer management that lets Claude edit files through Neovim's buffer system rather than directly on disk. These integrations respect Neovim conventions and work alongside other popular plugins like LSP clients, treesitter, and completion frameworks.
Terminal-first integration is the foundation that all IDE integrations build upon. Since Claude Code runs as a CLI application, it works with any editor that provides an integrated terminal panel. This means Emacs users can run Claude Code in an ansi-term or vterm buffer, Sublime Text users can use the integrated terminal, and even browser-based editors like VS Code for Web or Codespaces can run Claude Code through their terminal emulators. The terminal approach offers the most flexibility but requires manual context switching between the editor and Claude.
The architecture of IDE integrations typically follows one of two patterns. Embedded integrations run Claude Code as a child process within the IDE, communicating through the WebSocket-based protocol to share context, receive edits, and coordinate file operations. Bridge integrations connect to a running Claude Code session in a separate terminal, synchronizing state between the IDE and Claude through file watchers, editor protocol URIs, and RPC calls. Embedded integrations offer tighter coupling and faster response times, while bridge integrations provide more flexibility and work across multiple editors simultaneously.
When choosing an IDE integration, consider your primary workflow patterns. If you spend most of your time in a single editor and want the tightest possible integration, choose the native plugin for your IDE. If you frequently switch between editors or work across multiple projects, a terminal-based workflow with optional IDE bridging may be more productive. For pair programming and team settings, integrations that support session sharing allow multiple developers to interact with the same Claude conversation from different editors.
This directory contains 11 verified IDE integrations spanning every major development environment. Each integration has been tested for stability, feature completeness, and compatibility with current editor versions. Browse the collection below to find the integration that matches your editor and workflow preferences.