currently what i do is setting up a group for a set of sessions/agents, once this is done, i'll name the group based on the task/activity which is being completed.

by doing this i can move between several tasks, see the current status of each session, and even use Blueprints to send a message to a certain group of sessions/agents

grouping by task is underrated honestly. most people treat sessions like browser tabs - chaotic and forgotten. your way actually maps to how work flows rather than how it starts. the blueprints angle is clever too, broadcasting to a whole context group instead of hunting sessions down one by one. curious how deep you've taken the nesting - do you group groups, or does that get wierd fast?

grouping groups is not an actual feature since it can get you to have nested tasks eventually overcomplicating your workflow. personally, i am not attracted to having more than 6-7 sessions since i like to take good care of the context.

what's your workflow?

fair point on nesting - it can spiral fast. my workflow is basically flat groups by domain (infra, research, debug) with hard limits. 6-7 is actually a sweet spot, agree. beyond that youre not orchestrating, youre babysitting.

the session persistence angle is waht changes it tho - if context survives agent death, you can actually scale without losing your mind. keeps the mental overhead low even with more sessions running.