I’m coming over from 2.0 to 3.0 and trying to get to grips with multi agents in one window.
My workflow for 2.0 was to have different instances of Cursor open on two different folders of the same app. This meant that I could have each agent working on features independently that I could then test at the same time on essentially 2 different instances of the same app.
But I notice under 3.0 UI with all agents in one screen, the ‘Workspace’ grouping seems to group by git repo vs independent folder on my computer. Which then makes it hard to track what’s what. I’m sure this is a ‘solved’ problem, I just need to get up to speed with the best practice. So.. what is it?!
You’re right that the new Agents Window has a limit of 1 open window at a time, and you currently can’t have multiple windows working in the same or different repos.
You can however, have multiple agents working on the same repo or within different folders of the same repo but yes, you’ll need to tab between them on the sidebar. To help with keeping track of which is which, you can pin one or more chats to the top.
We are also working on enhancing support in the Agents view for multi root workspaces.
My development environment is set up in a such a way that i have a separate clone of my repository per feature which means I have to open a separate IDE per workspace.
I was excited about the new agent panel until I realized that all the threads are grouped by its git origin and not by the workspace folder which makes it impossible to separate my agents by feature.
If there was a way to organize the agents by the folder I would be very excited to use the new interface.
I wonder if the simpler fix here is just better branch management inside Agents.
A lot of the old workarounds were basically ways to keep agents working independently across different feature branches. If each agent could just have its own branch context, and we could tab between branches / monitor them in one place, I think that would solve a lot of this pretty neatly.
Feels like a small shift in the model, but it would make the new view much more powerful for parallel work.
