Same... I use herdr to manage 12+ sessions easily. There's no GUI that can do that.
I guarantee they're just starting a bunch of half baked random projects, abandoning them half way through and starting 12 new ones.
Less then half were daily projects, others ocassionally.
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.
Something like Orca's Agent Dashboard, or something else? https://www.onorca.dev/docs/model/agents-sessions
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".
You cannot put them next to code being changed but the code viewers are contextual to the session.
I am struggling to see a major difference let alone major advantage of herdr