I am relatively junior but I feel like I see more people working on one ticket at a time, with maybe 2 sessions open.
Curious how many people are juggling 6+ agents and do many jira tickets and orchestrating all these sessions.
1–9 of 9 posts
I am relatively junior but I feel like I see more people working on one ticket at a time, with maybe 2 sessions open.
Curious how many people are juggling 6+ agents and do many jira tickets and orchestrating all these sessions.
I usually limit # of concurrent tmux windows 15 (per Kanban limit of Work In Progress concept) but I've been known to up that to 30 when on-call.
I sometimes keep 4-5 active sessions going plus a couple waiting in the queue. Can't say it's always convenient. I don't know about others but I sometimes forget which session is doing what and end up getting confused.
I sometimes keep 4-5 active sessions going plus a couple waiting in the queue. Can't say it's always convenient. I don't know about others but I sometimes forget which session is doing what and end up getting confused.
I sometimes keep 4-5 active sessions going plus a couple waiting in the queue. Can't say it's always convenient. I don't know about others but I sometimes forget which session is doing what and end up getting confused.
Once you have 4–5 active agent sessions, the bottleneck becomes remembering who is doing what and jumping between them.
ai-devkit gives each agent a name, lets you see and navigate active sessions from one place, agents can communicate with each other, search sessions that you already completed. I also added remote control so I can check or redirect sessions without constantly switching terminals.
If you have time or chance to try it out, I would love to know what you think.