Claude Code /ide: Connect to VS Code and Work Inside Your Editor

Using Claude Code from the terminal, things like "which file am I looking at" or "is the code I just changed reflected on screen" keep breaking up. Switching back and forth between the terminal and editor windows disrupts your flow. What smooths this out is code-editor integration, and the command that handles its state is /ide.

Definition (What It Is)

/ide is a command that checks and manages the integration state between Claude Code and your code editor (IDE).

An IDE (Integrated Development Environment) is an editor that bundles writing, running, and debugging code into a single program. VS Code and Cursor are typical examples. /ide shows and manages whether Claude Code is properly connected to such an editor and which editor it's attached to.

Once integrated, Claude Code can know which file is currently open in the editor or what code you've selected, making work far more natural.

How to Use It (By Difficulty)

Basic — Checking the Integration State

Just type it.

/ide

This shows which editor you're currently connected to, or — if not connected — which editors you can attach to.

Intermediate — Attaching to VS Code

The most common case is integration with VS Code. Usually, installing the Claude Code extension inside VS Code integrates it automatically, but you can use /ide to inspect the connection state and, if needed, choose the connection directly.

/ide

Pick the editor to connect from the list. Once integrated, if you ask Claude Code a question while code is selected in the editor, it understands what "this part" refers to even if you just say that.

Advanced — Building an In-Editor Workflow

Once integration is done, you can change the habit of viewing terminal and editor separately.

1. Drag to select the code you want to fix in the editor.
2. Ask Claude Code something like "tidy up this function."
3. Claude Code works based on that selected region.

You need to type out file paths or copy-paste code far less. The fewer times your hands move back and forth, the less your concentration breaks.

Common Pitfalls

• If you type /ide and your editor doesn't appear in the list, first check whether the Claude Code extension is installed on the editor side. Integration requires both sides to be ready.
• Having multiple editor windows open at once can make it confusing which one to attach to. Settling on a single working window keeps it clean.

Real-World Example

A beginner developer using Claude Code in the terminal got worn out from constantly explaining paths like "the file I'm looking at now is styles/main.css..." After integrating with VS Code via /ide, just saying "tidy up the color values in this file" worked while the file was open in the editor. The time spent explaining dropped sharply, speeding up the work.

Taking It Further

Editor integration is part of refining your work environment. To overhaul your settings overall, look at /config for Claude Code settings, and to tidy up the terminal environment itself, use it alongside the /terminal-setup family of commands. Attach your editor with /ide, and tune the rest of the environment to fit your hand.

Summary

/ide is a command that checks and manages the integration state between Claude Code and your code editor. Attaching it to an editor like VS Code lets you work right within the editor's flow, without explaining or copying code piece by piece. If you're worn out switching between terminal and editor, this is the first thing to fix.

Based on: Claude Code v2.1.154 (2026.05)