Parallel agents in Zed

· ai tools programming · Source ↗

Article

TL;DR

Zed ships parallel AI agents in isolated git worktrees with a redesigned thread-first UI layout.

Key Takeaways

  • Each agent thread gets its own worktree; prevents file-stomping across concurrent agents
  • Architectural drift unsolved: parallel agents still independently rename types inconsistently
  • Zed is agent-agnostic and repo-agnostic — key differentiator from first-party Claude/Codex UIs

Discussion

Top comments:

  • [jamie_ca]: Lifecycle hooks let him auto-clone and delete Postgres DBs per worktree session
  • [ArielTM]: Worktrees solve file collisions; architectural consistency across agents is the hard unsolved problem

    Agent A renames a type to X. Agent B, in a different worktree, independently renames the same type to Y because neither saw the other’s decision. When you merge, neither worktree is ‘wrong’ but the code is inco

  • [verse]: Default layout pushes the file tree aside; would have repelled him as a new user
  • [2001zhaozhao]: Surprised Zed shipped this given their editor-first positioning; agent-agnostic is the real advantage

Discuss on HN