Concurrent Agent Chat Windows (tabbed agent threads) #42381
Replies: 46 comments 12 replies
|
I keep running cursor on the background only to have Codex there researching a feature, while Zed can be occupied with Claude Code task. |
|
This is really nice. Some other prior art that could be considered for the agent panel is the UI/UX that is also used in "Agent Manager" in the Antigravity editor https://antigravity.google/docs/agent-manager |
|
Just searched for this feature in the Zed settings. Sadly it is not there, but so cool that it is already implemented and a PR created. |
This comment was marked as spam.
This comment was marked as spam.
|
Any news on this? Definitely a much needed feature, I'm currently running a custom solution that basically does the same thing. An official update would be good. |
This comment was marked as spam.
This comment was marked as spam.
|
Just installed Zed coming from Cursor. The tabs are needed for sure. It's also uclear to me how to start a new thread with the current provider. When I click the "+" the Anthropic API route is not there so I have to go to "settings -> click on provider -> start new thread" Am I doing something wrong? |
|
+1 on this! Coming from Cursor as well, love the UI and how minimal the IDE is. But having only 1 thread at a time really slows down development. Currently have to use CC on another terminal while Zed runs. |
|
Would welcome such a feature. Its very limiting to run only one agent task at a time. |
|
This would be a game changing feature for sure. Can we get this released ASAP please? |
|
I'm currently working in the console versions of Codex and Claude Code, handling 6 or more tasks in parallel. How can I switch to Zed after this? The feature for multiple agents is definitely needed. |
|
100% needed! I love zed but the ability to use just one agent like is slowing me down hugely. |
|
I really need this..! this is keeping me from switching from vscode |
This comment was marked as spam.
This comment was marked as spam.
|
yes - we need this! |
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
|
I mean, guys, you can simply use the terminal tabs. Either way, the UI is
simply a wrapper around a CLI tool.
…On Fri, Feb 27, 2026 at 11:43 AM Kelvin Portuphy ***@***.***> wrote:
We all need this ASAP...
—
Reply to this email directly, view it on GitHub
<#42381 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AZZOTD5OM4FHS25ADJXVN734OAUVJAVCNFSM6AAAAACLWIHDZ2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKOJUGYYTANQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
This comment was marked as spam.
This comment was marked as spam.
|
Cursor has this and I use it a lot. Not sure why this is still not implemented - there is definitely a lot of interest. Also, this (sort of) fixes:
I created my own version with claude: https://github.com/SarthakMishra/zed/tree/feature/agent-panel-tabs agent-pannel-tabs.mp4
I have no experience in Rust, so if someone who knows what they are doing want to take it from here then please go ahead. |
|
This is a needed feature. It looks like several have already implemented it on their own, lets get it in! |
|
Please someone share any workarounds or tricks for this issue. |
|
Tabbed agent threads solve the UI problem. The thing I notice is that parallel threads raise the cost of unclear prompts: with one thread you can clarify mid-run, but with four running at once you want each one to start from a solid spec. The pattern that helps me: decomposing each starting prompt into typed blocks (role, objective, constraints, output format) before spawning a thread. Structured input means fewer interruptions across concurrent runs. I built flompt around this idea, a visual prompt builder that decomposes prompts into 12 semantic blocks and compiles to Claude-optimized XML. Open-source: github.com/Nyrok/flompt The tab-per-thread model in Zed could pair naturally with a typed prompt per tab, so each thread starts from a clear spec rather than a freeform question. |
|
The new Jetbrain's Air IDE looks really nice to work with multiple agents in parallel: https://air.dev/ A change here is really desperately needed. Being able to reference old sessions is a helpful start but still really buggy (you sometimes see sessions from other projects that will give you an error when clicking on them and at least for Claude Agent the sessions are often poorly named with no option to change the name, which makes it hard to find old threads). But coding with AI is really at the point where not being able to work with multiple agents in parallel is a dealbreaker... sad to say this as I really love Zed so much as an editor. |
|
As mentioned in here this is something we're actively working on. |
|
Hey all, parallel agents have now shipped in v0.233.5. 🎉 While this specific request was for a tab-based UI, we landed on a new sidebar design instead and we don't plan to pursue a tab-based implementation at this time. That said, the underlying capability you're after is here: you can run multiple agent threads in parallel. If you hit any bugs, please open an issue. |
|
Looks fantastic, thanks!!! Way better than tabbed - pretty sure it was a
suggestion from thinking inside the box.
…On Wed, Apr 22, 2026 at 10:29 PM Joseph T. Lyons ***@***.***> wrote:
Hey all, parallel agents have now shipped in v0.233.5
<https://zed.dev/releases/stable/0.233.5>. 🎉
You can read more about it in our blog post
<https://zed.dev/blog/parallel-agents>.
While this specific request was for a tab-based UI, we landed on a new
sidebar design instead and we don't plan to pursue a tab-based
implementation at this time. That said, the underlying capability you're
after is here: you can run multiple agent threads in parallel.
If you hit any bugs, please open an issue
<https://github.com/zed-industries/zed/issues/new?template=10_bug_report.yml>
.
—
Reply to this email directly, view it on GitHub
<#42381?email_source=notifications&email_token=AKYOW73D2FDMUGB5Q5XBA4D4XETRZA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNRWG42TCNJZUZZGKYLTN5XKOY3PNVWWK3TUUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-16675159>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AKYOW74XHZBRK4F4RSKXDB34XETRZAVCNFSM6AAAAACLWIHDZ2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMNRXGUYTKOI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|


Uh oh!
There was an error while loading. Please reload this page.
TL;DR: I added a tab bar to the Agent panel so you can run multiple agent threads in parallel (Zed native or external agents) and jump between them without losing context or scroll position. Great for long-running tasks, multi-prompt workflows, and deep backscroll review.
I would like to share some experience with it. This will really help me kick off a long-running task with one agent, then ask a different agent (Claude Code, Codex, Gemini CLI, etc.) something unrelated in another tab—no blocking, no context loss. And when you hop away from a lengthy conversation to another thread and return, you land exactly where you left off instead of snapping to the bottom. The UX will be familiar with you since the Agent panel’s tab bar behaves like Zed’s main editor tabs, so it feels native from day one.
Here is a quick demo recording for my current implementation
official.agent.panel.tabs.management.mov
What’s in the branch
Example flows this PR will unlock
I would like to hear any feedback on this new design. Is this something people will find helpful or is there anything we can improve on top of it? I am also excited to further discuss this design with Zed team to confirm this is what we are planning to do on the Roadmap.
Thanks for taking a look!
All reactions