Claude Code in VS Code: Terminal and Extension

Claude Code runs in VS Code two genuinely different ways — through the integrated terminal, and through an official extension with deeper editor integration. Both matter, for different reasons.

Via the integrated terminal (from the Terminal & Tasks course), Claude Code works exactly as it does anywhere else. Run claude in VS Code's terminal panel, inside your actual project — the same agentic capabilities (reading your codebase, planning, editing files, running commands) as any other terminal, just without leaving the editor.

The official Claude Code extension adds deeper editor integration beyond the plain terminal experience. Diffs from Claude's proposed changes can render directly in VS Code's native diff viewer, file references can link straight to the actual file/line, and — depending on the extension version — a dedicated panel keeps the conversation visible alongside your code rather than sharing space with your terminal.

This is a genuinely different situation from the Visual Studio Mastery track's equivalent course, where Claude Code is terminal-only (no extension exists for classic Visual Studio). VS Code's broader extension ecosystem gives it the deeper integration; the underlying agentic capability is otherwise the same tool either way.

Not GitHub Copilot — the same disambiguation as every other AI-agent-focused course in this platform. GitHub Copilot is a different, real tool with its own extension and its own interaction model; this course covers Claude Code specifically, matching how this platform (and Securafy's own developers) actually work.

The mental model from every other AI-agent course in this platform holds here too: direct it like a capable developer, don't just accept suggestions. Clear goals, real context, and reviewing its output like a teammate's pull request — the habits, not just the tool, are what actually matter.

Why this matters for you

Knowing both paths exist — plain terminal versus the extension's deeper integration — means you can choose based on what a specific task actually needs, not just default to whichever you tried first.

▶️ Before the next lesson

If you don't already have Claude Code installed, install it, and try running claude in VS Code's integrated terminal inside one of your real projects.