Well I don't use as many instances as they do, but using codex for example will take some time researching the code. It mostly just becomes a practice so that I don't have to wait for the model, I just context switch to a different one. It probably helps that I am ADHD, I don't pay much of a cost to ping pong around.

So I might tell one to look back in the git history to when something was removed and add it back into a class. So it will figure out what commit added it, what removed it, and then add the code back in.

While that terminal is doing that, on another I can kick off another agent to make some fixes for something else that I need to knock out in another project.

I just ping pong back to the first window to look at the code and tell it to add a new unit test for the new possible state inside the class it modified and I'm done.

I may also periodically while working have a question about a best practice or something that I'll kick off in browser and leave it running to read later.

This is not draining, and I keep a flow because I'm not sitting and waiting on something, they are waiting on me to context switch back.