Field noteNov 5, 20265 min read1 source

Zed publishes October Diff: Delta Claude Code sharing, remote MCP, nested subthreads

In one minute

Zed Industries’ October update to Delta adds a Claude Code plugin for sharing agent sessions, remote MCP server connections, and deeper subthreads. For teams, the important shift is that a colleague can take over an in-progress task in their own Claude Code session, while agents can reach tools such as GitHub, Linear, and Figma through MCP.

What changed: Delta’s October update adds remote MCP support, nested subthreads and teammate @mentions alongside the previously reported Claude Code sharing and Delta CLI.

What happened

In a post dated November 5, Zed Industries described a set of Delta updates for October. The headline integration is a Claude Code plugin that connects Delta’s collaboration features to the CLI tool. To set it up, users add the zed-industries/delta-claude plugin marketplace and install delta@zed-industries. From a project’s Git checkout, a user starts a Claude Code session and runs /delta share; a teammate with the plugin can use /delta join <link>. The teammate can pick up the work from their own Claude Code session or from Delta. The post says plugins for Zed, Pi, and Codex are in progress, and that other integrations can be built using the CLI.

Delta also now supports remote MCP servers, which give an agent access to tools from external services. The Settings > MCP > Available tab lists preconfigured servers including Figma, Linear, Cloudflare, and GitHub. Users can add servers not in the catalog through Add Custom Server. Delta detects authentication requirements by default; users can also configure OAuth with their own client ID and, optionally, a client secret.

The update expands the thread model. Users can run /fork inside a subthread to create another subthread, and can start a review or run /land from within one. When an agent opens a subthread to delegate work, users can talk to it there and steer its work. Zed presents subthreads as a way to explore alternatives, catch up on a teammate’s thread, or parallelize work without cluttering the main discussion.

Other changes include @mentions for organization members, which trigger an operating-system notification when enabled and also appear in Delta’s inbox; multiple inline terminals per thread; and a mobile layout for Delta Web. Settings and provider API keys now sync across accounts or desktop installations. Zed says its Quality Week resulted in more than 70 closed issues, with fixes including long-line diff responsiveness and saved-settings recovery. The post does not state a price or availability restriction for these features.

What the archive adds

A previous Field Note, “Delta (from Zed) makes Claude Code sessions multiplayer with /delta share”, covered beta sharing of Claude Code conversations and worktrees via /delta share and /delta join. This is a follow-up with more detail on the plugin setup and additional October capabilities, not a wholly new story.

Trend signal

This update supports agent protocols become the interoperability layer: Delta is adding remote MCP connections and a CLI-based path for integrations across different agent tools. The support is concrete but early; the post names a catalog of servers and future plugins, not a broad interoperability outcome already demonstrated across many environments.

Why now

Zed says attendees at AI Engineer NYC wanted shared conversations and code inside their preferred harnesses. The company says it expanded the CLI and built its first plugin for Claude Code in response. The post presents this as a product response to feedback, rather than explaining a wider market or technical deadline.

Why it matters

Agent work often becomes a team problem as soon as a task needs review, a handoff, or parallel investigation. Delta’s sharing flow lets a teammate continue from their own Claude Code session rather than requiring both people to use the same interface. Nested subthreads provide a place to delegate or explore without mixing every branch of work into the main conversation.

Remote MCP support adds another practical connection point: a team can expose tools from services it uses, including the named Figma, Linear, Cloudflare, and GitHub servers. That makes integration and authentication setup part of the workflow teams should evaluate, rather than assuming that a connected agent can safely or correctly use every tool. The value will depend on how reliably these handoffs preserve useful context and how teams govern access to remote services; the announcement does not provide usage data or a measured productivity result.

Limits and uncertainty

The source is a product update from Zed Industries and describes capabilities, not independent evaluations. It gives no price, plan requirements, rollout status beyond the note that Delta is now in beta, usage figures, or security review details for shared links and remote MCP connections. It does not establish how much context is preserved in a handoff, whether access can be scoped per teammate or tool, or how the integration behaves across larger teams. Zed’s plugins for Zed, Pi, and Codex are described as forthcoming, not available now.

Reader takeaway

For teams using Claude Code, Delta’s plugin offers a concrete way to hand an in-progress session to a teammate in their own environment. Remote MCP and nested subthreads broaden the same collaboration workflow, but teams should verify access controls and handoff behavior before relying on it for sensitive or production work.

Evidence / sources

  1. 1delta.dev/blog/the-diff-2026-10
All Field Notes

Next reads

Read next

Open the graph
  1. 01topicClaudeExplore the claude topic hub.
  2. 02topicClaude CodeExplore the claude-code topic hub.
  3. 03topicMcpExplore the mcp topic hub.
  4. 04archiveField NotesOpen the latest editorial analysis.
  5. 05sourcesSourcesSee the original sources this archive cites.
Who read this page?Machine requests, hidden until opened

Loading the privacy-safe route aggregate...

Open the JSON contract