In this categoryClaude Code · 45
- How to Install Claude Code on macOSStart
- How to Install Claude Code on Windows Natively (No WSL)
- How to Install Claude Code on Windows with WSL
- How to Start Your First Project with Claude Code
- How to Create a CLAUDE.md File for Your Project
- How to Configure Claude Code with settings.json
- How to Layer Global, Project, and Local CLAUDE.md Files
- How to Set Up a Permissions Allowlist in Claude Code
- How to Use Claude Code Inside VS Code
- How to Add a Custom Slash Command in Claude Code
- How to Create a Custom Slash Command in Claude Code
- How to Pass Arguments to a Claude Code Slash Command
- How to Use Claude Code Slash Commands (Full List + Examples)
- How to Add Custom Slash Commands to Claude Code (Arguments + Frontmatter)
- How to Fix command not found After Installing Claude Code
- How to Add Any MCP Server to Claude Code
- How to Connect an MCP Server to Claude Code
- Best MCP Servers for Coding in 2026
- How to Add a Filesystem MCP Server to Claude Code
- How to Connect the GitHub MCP Server to Claude Code
- How to Create Your First Subagent in Claude Code
- Context7 Alternatives: MCP Servers for Up-to-Date Docs
- How to Manage MCP Server Scopes in Claude Code
- How to Restrict the Tools a Subagent Can Use
- How to Debug a Failing MCP Server in Claude Code
- How to Generate Unit Tests for a Function with Claude Code
- How to Refactor a Long Function Safely with Claude Code
- How to Debug a Failing Test with Claude Code
- How to Review Your Own Diff Before Committing with Claude Code
- How to Rename a Symbol Across the Codebase with Claude Code
- How to Review a Teammate's Pull Request with Claude Code
- How to Raise Test Coverage on a Specific File with Claude Code
- How to Debug a Runtime Error from a Stack Trace with Claude Code
- How to Add an Integration Test for an API Route with Claude Code
- How to Teach Claude Code Your Test Conventions with CLAUDE.md
- How to Find Which Commit Broke a Test with Claude Code
- How to Set Up Hooks for Automation in Claude Code
- Claude Code Hooks Explained: Events, Config, and Blocking
- How to Block Risky Commands with a Claude Code Hook
- How to Auto-Format Files After Edits with a PostToolUse Hook
- How to Get a Notification When Claude Code Finishes a Task
- How to Give a Coding Agent a Clear Stop Condition
- How to Make an Agent Plan Before It Edits
- How to Keep an Agent Session Focused by Clearing Context
- How to Pin a Specific Model for One Project
How to Use Claude Code Inside VS Code
Install the VS Code extension so Claude Code edits appear as inline diffs in the editor instead of only in the terminal.
Claude Code works in the terminal, but pairing it with the VS Code extension shows proposed edits as native diffs right in the editor, with your current file and selection passed in as context. This guide installs the extension and runs a change from inside VS Code.
What you need
- VS Code installed
- Claude Code CLI installed and signed in
- A project open in VS Code
- About 6 minutes
Step 1: Install the extension
Open the Extensions panel, search for Claude Code, and install the official extension from Anthropic. It detects the CLI you already installed.
Step 2: Open the Claude panel
After installing, open the Claude Code panel from the sidebar or the command palette. Run the Open Claude Code command to dock a session next to your files.
> Claude Code: OpenStep 3: Ask for a change with the file in context
Select some code or just keep a file open, then type your request. The extension passes the active file and selection automatically, so you can refer to this function or the selected lines.
Step 4: Review the inline diff
Edits appear as a native VS Code diff. Accept, reject, or keep refining, the same review loop as the terminal, but with full editor tooling around it.
Result: you get Claude Code's agent with VS Code's diff view, file tree, and search, which makes reviewing larger changes much easier than scrolling a terminal.
Watch related tutorials
9:47
26:11
24:18
1:42:18
28:14
41:09New guides in your inbox
Fresh step-by-step how-to guides as we publish them. One email a week, no more.