Parallel Agent Execution in Zed : Coding at the Speed of thought.

[cs50victor]

Following up on #33132 from June - I've been thinking about the architectural concerns raised and believe there's a lighter-weight path to multi-agent support that could ship sooner.

What's changed since June:

• The agent ecosystem has matured significantly
• More users are hitting the "waiting on AI" bottleneck daily
• Patterns for effective multi-agent workflows have emerged from heavy usage

Minimal viable approach that sidesteps the concerns:

Instead of deep architectural changes, we could start with a simple response queue:

• When you send to Agent A, auto-switch to Agent B if it has a ready response
• No complex delegation UI - just Alt+Send to stay on current agent
• Use existing git worktrees for natural isolation (no new checkpoint system needed)
• Single input bar that can target multiple agents (like addressing multiple people in Slack)

This preserves Zed's "speed of thought" philosophy - you're never waiting, always reviewing or
writing. The implementation touches mainly acp_thread for queuing and adds a thin orchestration
layer.

Why revisit now:

• Users are naturally opening multiple Zed instances to work around the single-agent bottleneck
• Massive productivity gain with parrallel agents.
• Small initial implementation could inform the eventual "proper" architecture

Would the team be open to exploring this lighter approach as a stepping stone? I understand the
previous concerns about doing it right, but even this minimal version would be transformative for
daily workflows.

Timeline-wise, could this fit into early 2025 roadmap? Happy to help prototype or test.