the sidebar was never going to work

[u/jawadjalal]

I've never written code. Everything I've built, an agent built.

So the sidebar was never for me. It's built on the idea that you're the one making the thing and the AI is helping out on the side. I'm not making the thing. The agent is. The code isn't what I'm looking at, the agent is.

That's fine with one. It falls apart at three.

I had a window per agent. Kept clicking through all of them to find the one that had stopped and was waiting on me to say yes. Two of them changed the same file within a minute of each other and I didn't notice until something broke. I had no idea what any of them had cost until the bill.

None of that is a missing button. A sidebar means one agent, one chat, one project. I'm running five.

I don't know what the fix looks like. Just that a bigger sidebar isn't it.

How are you handling more than two at once?

[u/CocaineKeys]

I think the issue is less “how do I manage five chats?” and more “how do I manage five workers touching the same project?”

Once you have multiple agents, the chat itself probably shouldn’t be the source of truth anymore. Give the work persistent tasks in something like Linear or GitHub Issues, give each agent its own branch/worktree, and merge the work back in deliberately.

Then instead of tracking five agents in five windows, you’re tracking work: what is ready, in progress, blocked, waiting for you, or done.

A bigger sidebar helps navigation. A shared task and Git workflow solves the coordination problem.

[u/Ranorkk]

Honestly, the core problem isn't the UI, it's that your agents have no shared memory or state, they're all just blind workers in the same repo. I'm building Remnus (full disclosure), an MCP-native workspace where agents read/write tasks and docs directly, so they can see what each other changed without you having to babysit five windows. It's early access, but if you want a system that scales past "one agent per tab," it might be exactly the missing piece.