Parallel Agents in Zed

Article

TL;DR

Zed ships parallel agent threads with isolated worktrees, letting multiple agents work a codebase concurrently.

Key Takeaways

• Agent-agnostic: works with Claude, Codex, and others — not locked to one provider
• Worktrees give each agent isolated DB and config, preventing agents from trampling each other
• New UI pushes file tree aside for agents — alienating users who don’t want AI-first layout

Discussion

Top comments:

• [jamie_ca]: Lifecycle hooks + isolated Postgres per worktree is the real workflow unlock
• [2001zhaozhao]: Key advantage: agent-agnostic and supports multiple repos per agent via auto worktrees
• [verse]: New layout buries the file tree — would have turned me off as a new user
• [danielvaughn]: What’s really needed: stateful file layer with locking so agents don’t overwrite each other

Discuss on HN