Skip to content
BSWEN
Blog

What Claude Code Features Are Missing in the VS Code Extension? (Complete Comparison)

Cowrie
Cowrie
Dev @ Bswen

I switched to Claude Code CLI after struggling with the VS Code extension for weeks. The extension kept disconnecting from my MCP servers, certain slash commands wouldn’t work, and I couldn’t access Opus 4.6. Here’s what I discovered about the differences.

The Problem Started With MCP Servers

I was trying to connect my local MCP server through the VS Code extension. It worked perfectly in the terminal with Claude Code, but the extension just wouldn’t recognize it.

MCP Server Connection Comparison
# Terminal (Claude Code) - Works perfectly
claude> connect to local-mcp-server
✓ Connected to local-mcp-server


# VS Code Extension - Nothing happens
> No MCP servers found

After digging through Reddit discussions and documentation, I found I wasn’t alone. The VS Code extension is consistently behind the terminal version in features and functionality.

Missing Feature #1: MCP Server Connectivity

Model Context Protocol (MCP) servers are critical for extending Claude’s capabilities. They allow Claude to connect to external tools, databases, and APIs.

MCP Architecture Comparison
┌─────────────────┐     ┌─────────────────┐
│   Claude Code   │────▶│   MCP Server    │
│     (CLI)       │     │  (PostgreSQL)   │
└─────────────────┘     └─────────────────┘
         │                       │
         │    ✓ Full Access      │
         └───────────────────────┘


┌─────────────────┐     ┌─────────────────┐
│ VS Code Ext.    │────▶│   MCP Server    │
│                 │  ✗  │  (PostgreSQL)   │
└─────────────────┘     └─────────────────┘

One Reddit user noted: “I prefer the extension UI so I can read Claude’s Thinking blocks, but I cannot get it to connect to any MCP servers, so I switch back and forth.”

Why this matters: Without MCP connectivity, you lose access to:

  • Custom database integrations
  • External API connections
  • Local file system operations
  • Custom tool implementations

Missing Feature #2: Slash Command Support

Slash commands provide quick access to powerful features. In Claude Code CLI, I use these daily:

Common Slash Commands
/commit     - Create a git commit with auto-generated message
/review-pr  - Review a pull request
/pr         - Create a pull request
/tdd-guide  - Run test-driven development workflow

But in the VS Code extension, several of these commands either don’t work or behave inconsistently. The extension documentation doesn’t even list all available commands, making it a guessing game.

Trial and Error Process:

  1. I tried /commit in VS Code - worked sometimes
  2. I tried /review-pr 123 - returned empty response
  3. I switched to CLI - everything worked immediately

Missing Feature #3: Model Availability (Opus 4.6)

This one caught me by surprise. I had been using Opus 4.6 in the CLI for complex reasoning tasks:

Model Availability Comparison
# CLI - Opus 4.6 available
claude --model opus-4.6 "Analyze this architecture"


# VS Code Extension - Opus 4.6 not listed
# Only shows: Sonnet, Haiku, Opus 4.5

A Reddit user confirmed: “Strange thing is now you can’t use Opus 4.6 in the vs code extension. But you can use it in Claude code.”

Why Opus 4.6 matters: It offers deeper reasoning capabilities for:

  • Complex architectural decisions
  • Multi-file refactoring analysis
  • Debugging intricate interactions

Missing Feature #4: Effort Slider Functionality

The effort slider controls how much reasoning effort Claude applies to a task. It’s critical for balancing quality vs. speed.

Effort Levels Visualization
Effort Levels:
────────────────────────────────────
Low     |████░░░░░░░░░░░░░░░░| Fast, basic
Medium  |████████████░░░░░░░░░| Balanced
High    |████████████████████| Deep reasoning

In the VS Code extension, the effort slider exists but doesn’t work correctly. Another user reported: “I’ve found there are number of bugs with the vs code extension… effort slider not working correctly.”

Impact: You might think you’re getting deep analysis when you’re actually getting shallow responses.

Missing Feature #5: Project-Wide Operations

This is where Claude Code CLI truly shines. It operates on your entire project with session memory.

Architecture Comparison
┌────────────────────────────────────────┐
│         Claude Code (CLI)              │
├────────────────────────────────────────┤
│ • Multi-file understanding             │
│ • Session memory (remembers context)   │
│ • Agents invoking other agents          │
│ • Custom slash commands and skills      │
│ • Hooks that fire on tool events        │
└────────────────────────────────────────┘


┌────────────────────────────────────────┐
│       VS Code Extension                │
├────────────────────────────────────────┤
│ • Single file focus                    │
│ • Limited session persistence           │
│ • Basic commands only                  │
│ • No custom skills support              │
└────────────────────────────────────────┘

Real-world example: When I asked Claude to refactor a function across 15 files:

  • CLI: Found all usages, updated imports, handled edge cases, committed changes
  • VS Code Extension: Only updated the current file, missed usages in other files

Permission Bypass Issues

The VS Code extension also has problems with permission bypasses. When running operations that need elevated permissions:

Permission Handling Comparison
# CLI - Clear permission handling
⚠ This operation modifies 15 files. Continue? [y/N]


# VS Code Extension - Silent failures or confusing prompts
> Operation failed (no clear reason)

Comparison Summary

Feature Comparison Table
Feature                    | CLI    | Extension
---------------------------|--------|----------
MCP Server Connectivity    | Full   | Limited/Broken
Slash Commands             | Complete set | Partial support
Opus 4.6 Model             | Available | Not available
Effort Slider              | Working correctly | Buggy
Project-Wide Operations    | Full session memory | Limited scope
Custom Skills              | Supported | Not supported
Hooks System               | Full tool event hooks | Not available

When to Use Each

Use Claude Code CLI when:

  • Working on multi-file projects
  • Need MCP server connections
  • Want custom skills and hooks
  • Require Opus 4.6 for deep reasoning
  • Running automated workflows

Use VS Code Extension when:

  • Quick single-file edits
  • Prefer reading Thinking blocks visually
  • Need IDE integration for simple tasks

My Current Workflow

I now use both, but strategically:

Hybrid Workflow Strategy
Morning: Claude Code CLI
──────────────────────────
• Complex refactoring
• Architecture decisions
• Multi-file operations
• Running /tdd-guide workflows


Afternoon: VS Code Extension
──────────────────────────
• Quick bug fixes
• Single file edits
• Code reviews (for Thinking block visibility)

How to Get Started with Claude Code CLI

If you’re convinced to try the CLI:

CLI Installation Steps
# Install Claude Code
npm install -g @anthropic-ai/claude-code


# Set up your API key
export ANTHROPIC_API_KEY=your-key-here


# Navigate to your project
cd your-project


# Start Claude Code
claude

The learning curve is worth it. After a week with the CLI, I found myself switching to the VS Code extension less and less.

Final Words + More Resources

My intention with this article was to help others share my knowledge and experience. If you want to contact me, you can contact by email: Email me

Here are also the most important links from this article along with some further resources that will help you in this scope:

Oh, and if you found these resources useful, don’t forget to support me by starring the repo on GitHub!

Comments

Tags: