Zed adds Parallel Agents, letting developers manage multiple coding threads simultaneously

Zed pushed its agent strategy a step further on April 22, adding Parallel Agents so developers can run multiple coding threads at the same time inside one window. The feature gives each thread its own agent, context window, and conversation history, and it puts access control front and center by letting users decide which folders and repositories each agent can see.

That design changes the feel of the editor from a single chat tied to one task into a managed workspace for overlapping work. The new Threads Sidebar is where developers start, manage, and switch between threads, while also stopping, archiving, and launching new ones without losing track of what each agent is doing. Zed said the sidebar groups active threads by project, which matters when parallel work starts to sprawl across repos, worktrees, and debugging sessions.

The interface shifts with that workflow. From version 0.233.0 onward, the Agent Panel and Threads Sidebar sit on the left by default, with the Project Panel and Git Panel on the right, and the sidebar opens with ctrl-alt-j. Existing users can opt into the new layout, but the default signals where Zed thinks serious agent work is headed: fewer hidden interactions, more visible supervision, and tighter scoping around what each model is allowed to touch.

The release also fits into Zed’s broader idea of agentic engineering, where the goal is not to replace the developer but to keep human craft in the loop while AI handles more of the mechanical churn. That shift is easier to justify when the company is publishing numbers of its own. On April 9, Zed launched Agent Metrics, a public weekly view of AI agent adoption and turn times inside the editor, including session counts, turn volume, and response-time distributions at p10, p50, and p90.

The Rust angle remains central. Zed has long described itself as built in Rust and designed for 120 FPS, with a scratch-built GPUI framework and GPU-accelerated UI work to keep the editor responsive. Parallel Agents extends that same performance-first logic into the AI layer: if the editor is going to host several live threads at once, the interface has to stay legible as the workload grows.

Zed had already been laying the groundwork. Its April 1 stable release added support for pasting files and folders into the Agent Panel, and its February 25 release added session history for external agents plus agent panel restoration so threads survive editor restarts. On Hacker News, commenters singled out Zed’s agent-agnostic approach, its support for multiple repositories through worktrees, and its native agent UI as signs that the product is leaning into the way serious Rust developers actually work. Parallel Agents makes the tradeoff clear: the feature saves time when tasks can truly run in parallel, but it only pays off if the editor keeps the overhead visible and under control.