Comment by scottmessinger

21 hours ago

I love Zed and have been using it for years. I’ve been especially excited about multi-agent support—it feels like it could be a genuinely powerful model.

That said, the current UX is pretty confusing.

There’s a mismatch in visual hierarchy: selecting an agent in the sidebar appears to change the entire editor’s worktree/branch, but the worktree/branch selector lives in the window titlebar, which strongly implies it controls the whole window. So it’s unclear which is the source of truth—the agent or the window.

That ambiguity shows up in the workflow too. If I want to create a new branch/worktree and then start an agent on it, I can’t do that directly. I have to:

1. create an agent 2. start a conversation (to instantiate it) 3. then switch the branch/worktree

That ordering feels backwards—I’d expect to define the context first, then start the agent.

Even basic navigation is unclear. If I switch the branch in the titlebar, does that affect the current agent, or the whole window? If I want to return to a previous worktree, is that tied to the agent or not? I still don’t have a solid mental model.

It feels like there are two competing concepts:

* agents as independent workspaces * the window as the workspace

Right now they overlap in a way that’s hard to reason about.

The feature has a lot of promise, but the current UX makes it difficult to predict what’s going to happen, which makes it hard to rely on.

I do like the new UI, it beats having a window per workspace, IMO. But personally I'd rather the workspace switcher be based on the project explorer than the conversation history.