This seems to be the new meta for a segment of the HN crowd, and I'm struggling to understand how it works. I'm at most having 4 sessions parallely, and even then I am burned out after a full day of this. How can you keep up with what all the agents are doing?

From the people around me doing this - they aren't keeping up, they aren't looking at the finished project/product, then throwing it over the wall for others to triage. Rinse and repeat. Definitely fits some people's personalities, but not mine.

I guess the main benefit of herdr is it essentially flags the state of agents and what needs attention. So you can have multiple ones running and quickly go to the ones that need an input.

I think there _is_ a way to do this nicely in a GUI btw, which I've been toying with as a side project. Basically... build it as a trello style board.

And it's not 12 projects, its multiple tasks, e.g. 'look at this crash for me', 'fix this extension in my pi env that is doing something bad', 'debug this high memory usage', etc. etc. It's easy to just fire tasks off and come back to them later. The project ones usually require more human focus ofc.

Now if only I could automate meetings like this.

I've found an agent to manage agents, plus aggressively creating skills/workflows helps.

The main agent is the entry point:

"review this PR" should open a new workspace and spin up one or more agents to do whatever review workflow you like.

"Implement ticket xyz" should open a new space, read the ticket content, plan/write/test/review/create a PR without much managerial input. You'll still need to answer questions and check work between steps, but all of the busy work can be done by your agent(s) with skills. If they get it wrong, update the skill.

Same for "research this bug report/product question/error trace".

It's a skill like anything. Context switching on this level is initially exhausting, but do it enough and it becomes natural.