How Claude Agent Works Differently in VS Code and Zed

Overview #

Both VS Code and Zed let you use Claude directly in the editor, but what looks like the same experience is built on fundamentally different architectures. This difference goes beyond mere implementation details — it affects which features are available and when updates arrive. The relationship between Anthropic and Zed is also somewhat different from what many people assume.

1. The Release Pace of Claude Code #

Claude Code is updated at a pace that is remarkable even by AI agent tool standards.

The Reality of Its Release Cadence #

Looking at the official Changelog, the picture for just the past one to two months is striking:

• The 2.1.x series alone has had over 50 releases (February–April 2026)
• Multiple versions in a single day are not uncommon
  • Example: 2.1.89, 2.1.90, and 2.1.91 were all released on April 1–2

What Each Release Contains #

Releases are rarely limited to bug fixes — a single release often bundles a large number of changes. For example, v2.1.89 (April 1, 2026) included:

• A new PermissionDenied hook
• A fix for Shift+Enter behavior in Windows Terminal
• A bug fix for prompt history containing CJK characters and emoji
• Security hardening for the PowerShell tool
• A fix for voice push-to-talk

…and more than 30 other changes merged at once.

This pace shows that Claude Code is still evolving rapidly.

2. How Claude Agent Differs Between VS Code and Zed #

Even though both editors offer “Claude in the editor,” the underlying architecture is fundamentally different.

VS Code Implementation #

The official VS Code extension works as a GUI wrapper around the Claude Code CLI. The extension itself only provides the interface; the actual agent processing is handled by the CLI that the user installs and updates manually. If you want the latest Claude Code at all times, just keep the CLI up to date.

Key characteristics:

• Direct file manipulation via the VS Code Extension API
• UI features such as inline diff, checkpoints, and @ mentions
• Shares the same authentication, model, and CLAUDE.md as the CLI

Zed Implementation #

In Zed, when you create your first Claude Agent thread, @zed-industries/claude-agent-acp is automatically installed. This package corresponds to both the “ACP Adapter” and “Claude Code SDK” boxes in the diagram. The ACP adapter handles communication with the Zed editor, and it contains a vendored version of the Claude Code CLI internally. Even if you have the claude command (Claude Code) installed separately on your machine, that version is not used.

Key characteristics:

• No separate Claude Code installation required
• Communication goes through a translation layer called ACP (Agent Client Protocol)
• The vendored version is updated on Zed’s own release schedule

Side-by-Side Comparison #

3. Feature Update Lag Caused by Architectural Differences #

The Structural Reason for Lag #

Zed’s vendored Claude Code depends on Zed’s own release cycle.

Zed’s release notes do not explicitly state the vendored Claude Code version number, making it difficult for users to know the exact lag. Based on the difference in update frequency, it is estimated that there is always a lag of one to two weeks (equivalent to 10–20 Claude Code releases).

Features More or Less Affected #

Workaround in Zed #

Zed’s documentation provides a feature to override the vendored binary by setting the CLAUDE_CODE_EXECUTABLE environment variable.

{
  "agent_servers": {
    "claude-acp": {
      "type": "registry",
      "env": {
        "CLAUDE_CODE_EXECUTABLE": "/path/to/claude"
      }
    }
  }
}

If you want to use the latest features in Zed, point this setting to a separately installed CLI and you will effectively get the same version as VS Code.

4. The Relationship Between Anthropic and Zed — The Reality of Their Collaboration #

Anthropic does not officially sponsor Zed, but there are deep technical and human ties between the two organizations.

How It Started (2024–) #

The relationship did not begin with a contract or investment — it started with an affinity of engineering culture. The Zed AI announcement blog post (August 2024) states:

Anthropic engineers discovered Zed and found value in its raw, text-oriented interface. Anthropic’s core team of Rust engineers began actively contributing to Zed’s open-source codebase.

The fact that Zed is written in Rust, and that Anthropic also makes heavy use of Rust, became the shared technical language that connected the two.

The Specifics of Their Collaboration #

Noteworthy: Anthropic Has Not Officially Adopted ACP #

Regarding ACP (Agent Client Protocol), which was developed by Zed, Anthropic itself has not formally adopted it. Zed independently built a bridge that wraps the Claude Code SDK with ACP, and in a September 2025 blog post called on the community to “ask Anthropic to bring the SDK up to feature parity with Claude Code, or to adopt ACP directly.”

The current situation has Zed actively playing the bridging role while Anthropic remains in a more reactive position.

Overview of the Relationship #

No capital relationship (investment, acquisition, etc.) has been publicly disclosed. The relationship remains within the bounds of a technical and commercial partnership.

5. Supplementary Topic: ACP — A New Standard Protocol #

What is ACP (Agent Client Protocol)? #

An open protocol announced by Zed in January 2026. Its goal is to connect AI agents and editors in a standardized way.

Adoption Status (as of April 2026) #

• Editor side: Zed (reference implementation), JetBrains (collaborative development), Neovim (plugin available)
• Agent side: Claude Code (via Zed adapter), Gemini CLI (direct integration by Google), OpenAI Codex

The Significance of ACP #

Previously, agent-editor integration was 1-to-1, case-by-case. If ACP becomes widespread, the relationship becomes m × n → m + n. In other words, implementing a single new agent makes it work with all ACP-compatible editors.

This standardization matters for Anthropic too, because it opens up the possibility of Claude Code spreading as an “agent usable across editors, not tied to any one.”

6. Summary: Which Should You Choose? #

VS Code If You Prioritize Latest Features and Stability #

If you want to benefit from Claude Code’s daily updates in real time, or want to try new features (hooks, Plan mode improvements, PowerShell tools, etc.) as soon as possible, VS Code + the latest Claude Code CLI is the optimal combination.

Zed If You Prioritize the Editor Experience #

If you are drawn to Rust’s exceptional speed (0.12-second startup, 120fps rendering), built-in multiplayer, and Zed’s simple, consistent editor design, Zed is an excellent choice. Setting CLAUDE_CODE_EXECUTABLE to use the latest CLI eliminates the version lag issue.

The Two Are Complementary, Not Competing #

VS Code and Zed each offer distinct value, and many developers actually use both. Using Zed as a daily editor while running heavy autonomous tasks with the Claude Code CLI in a terminal is a perfectly practical approach.

References #

• Claude Code Changelog
• Zed Stable Releases
• Zed External Agents Docs
• Zed ACP