VS Code-Native Workflows

The VS Code extension integrates with editor features that the terminal version cannot access: diagnostics, source control, terminal output, and the file explorer. When you ask Claude to fix errors, it can read the Problems panel directly — the same red squiggly lines you see in the editor. When you ask Claude to review changes, it reads the Source Control diff view. This integration reduces the amount of context you need to provide manually.

The diagnostics integration is particularly powerful. TypeScript errors, ESLint warnings, and other language server diagnostics are available to Claude without you pasting error messages. "Fix all the TypeScript errors in this file" works because Claude can see the same errors your editor shows. This is the workflow that most closely resembles pair programming — you see the error, Claude sees the error, Claude fixes it, you review the fix.

# Claude can access these VS Code features:

1. Problems panel  → Read TypeScript errors, lint warnings
2. Source control   → Read git diff, staged changes
3. Terminal output → Read build output, test results
4. File explorer   → Navigate project structure
5. Active editor   → Read the file you are currently viewing
6. Selection       → Operate on highlighted code

# Prompt example leveraging integration:
"Fix the TypeScript errors shown in the Problems panel
for the currently open file."