alt Hacker NewsI agree with the problem of complexity and context switching, but I don't see how having a single orchestrator agent helps with this problem.
Nowadays, agents run for hours on a serial task, so after telling the agent to start working on something, you simply cannot work on it anymore for a few hours. I don't see how there's anything you can do that rescues you from having to switch to something else then back a few hours later.
I think accepting that context switching will happen, and simply optimizing the UI/UX to make context switching as fast as possible, will be the way to go in the future. This will involve some form of cross-task aggregation, and eventually it will pay to have an agent decide what you should pay attention to next, but I think it will not be one regular agent you talk to, but some kind of specialized UI where you go through a backlog of pending tasks and decisions.
Agree — that is what the coordinator is. You start a task in a Project, and Claude spins up a thread to work on it. You can then do other work in the project in parallel. When Claude needs you or has a result, it will tell you in the main thread. The cool part of the UX is it feels like a better use of attention — I no longer feel like I’m mentally jumping between contexts.