> on different projects

This seems like an important caveat the author of the article failed to mention when they described this:

> you can have several agents running simultaneously - one building a user interface, another writing API endpoints, and a third creating database schemas.

If these are all in the same project then there has to be some required ordering to it or you get a frontend written to make use of a backend that doesn't have the endpoints used, and you get a backend that makes use of a different database schema than the separately generated database schema.

This is just project management. Teams of software devs have been doing this for decades. And it’s easier with agents because there is no harm in letting one sit idle.

On the same project you can use worktrees or otherwise separate clones of the repo - that part is not that bad. My comment was just about my own context switch.