Nathaniel Whittemore

The model is then smart enough to figure out which agents can work in parallel, or in the case that an agent requires the output of a different agent, how to run them sequentially.

Simon writes that you can monitor agents overall via a dashboard with progress indicators and also select individual agents to monitor their work.

One of the important things that Simon points out is that part of the big upgrade here is not just the performance, but the user experience.

He writes, when I think about something that would scale up to an enterprise, which will include a lot of users who won't be comfortable in something like Cloud Code in the terminal, this feels like it would be easily adopted.

It's extremely clear and intuitive.

The model gave Simon both not only the final output, but also all of the intermediate outputs from each of the distinct agents.

Now, Simon's big request and his caveat is that he wants access to connectors or MCPs as well as agent skills to be able to fully sync this with the larger ecosystem of data that people work in.

Overall, though, he says, I'm impressed.

I've been waiting for something like this that makes it easy for anyone, regardless of technical expertise, to ask AI to do something and have it complete the task with multiple agents playing different roles and working collaboratively.

This feels like the emerging future of humans managing teams of AI agents, the way they currently manage teams of other humans.

I honestly don't understand how Kimi got here first.

There are other solutions out there for agents to work together on tasks, but everything I've seen is too technical for the average user, requiring you to use the terminal or too rigid, requiring you to pre-build workflows.

How did Kimi create such a great model with such excellent agentic capabilities and build such an intuitive interface?

Now this is the interesting question, and why it makes me feel like we are very much seeing the beginning of a broader phenomenon around these agent swarms.

In addition to K2.5, I've seen a couple people talking about Cloud Code's new task system in this same context, and so it seems like something that's probably on the minds of those folks as well.

Langchain developer Sydney Runkle is also talking about this sub-agent's architecture, all of which makes me feel like 2026 might be the year of the agent swarm.

Indeed, there's enough chatter that Ethan Malek is making one last perhaps vainglorious attempt to steer us away from using the swarm terminology.

On Monday, he tweeted, Let's not call groups both terrifying and not a useful analogy.

Groups of agents should be called teams or organizations.

It both describes how to structure them and also how to use them.