Claude Code integrates into VS Code via official extensions that allow the Claude CLI to connect and manage tasks like code generation, debugging, and project assistance directly within the IDE.

Setting up Claude Code in VS Code

Install the official extension: Search for the official Claude Code extension in the VS Code marketplace and install it. This extension acts as an interface for Claude to interact with your project files. "Easiest way is just to choose an extension of your choice, login with your account or via api key and thats it."

Use the CLI within VS Code: You can also use the Claude Code CLI directly within the VS Code terminal. Opening a terminal inside VS Code and starting Claude Code effectively integrates it. "If you open a terminal inside VSCode and start Claude Code in it, you've got yourself 'Claude into VS Code'."

Configure permissions: Claude Code includes permission modes that can be cycled with Shift+Tab, including an "Accept Edits" mode for auto-approving file edits, a read-only "Plan" mode, and a "Bypass Permissions" mode for full automation. "Bypass Permissions mode (the closest to Codex Full Auto) skips all prompts."

Managing Token Usage and Cost

Choose appropriate models: Use Sonnet for most tasks, as it is considerably cheaper, and reserve Opus for complex tasks or for verifying Sonnet's work. "You don’t need to run opus for every little thing, 90% of the time sonnet will get you through and is considerably cheaper when it comes to usage."

Optimize prompts and context: Keep prompts concise, avoid excessive documentation, and be direct about the files Claude needs to access. Starting new chats for new topics also helps manage context and token usage. "larger prompts and context eat tokens so foe example if you fixed a bug, open a new ui to fix the next bug"

Leverage CLAUDE.md: Maintain a CLAUDE.md file with specific rules to guide Claude, helping it stay concise and avoid reloading context it already possesses. "Keep a short CLAUDE.md with your rules, give it only the files that matter, and ask for a brief plan first."

Alternative Workflows

Utilize the desktop app for complex projects: For very large projects, some Users find the Claude desktop application more stable for remote sessions and managing project-wide context. "I used Claude code in vs code remotely for some time, but the Claude app is much more stable for remote sessions"

Command Line Interface (CLI): Some Users prefer using the CLI in a wider terminal window for a less cramped experience, especially for planning and prompting conversations. "If you use the CLI you can still use remote control, and it’s just a nicer interface I think - wider window etc - I always feel like those skinny chat panes in VS code feel so cramped."

Is a more detailed explanation of the CLAUDE.md file helpful for optimizing Claude Code's performance?