The BIGGEST issue with using a team grok bots to orchestrate all my tickets via Codex sessions is that if my grok bok usage is running low with lots of Codex usage left, im stuck
@jayledev You should have a bot for a specific role, dont make your lead do everything (work, review, ticket scoping etc), my leadโs only responsibility is to orchestrate work, nothing else
I use the engineering lead bot by @poteto , it does a chase every 30min so no work is stuck forever.
For review, i have a Reviewer bot that checks the PR pumped out by the Engineer bot, checking for things like blast radius, bugs, tests, code quality, does it meeting the tickets requirements and so on
I thought AI would relieve us from work and stress but I noticed that I read and process information more than ever, more context switching, and managing more projects at the same timeโฆ
My lead does a chase routine every 30min to check on active tasks, open PRs and queue up tickets to work on (it picks up tickets assigned me).
Basically i look through my backlog and assign tickets to myself and the lead works through them and auto merges, if the change has a larger blast radius then itll flag it for me to manually review
Im using github issues to manage my tickets, ive set up blocking relationships so a ticket that depends on another cant be started.
I hope theyve improved grok bot context management so even after a restart, itd still know what it was up to before it shutdown. Its a shame (or blessing) that theyve hid away all the config and low level detail for the grok bots.
How did you know you bot was restarted anyway? Did you ask it?
whoever isn't using a team of personal AI assistants is sleeping on the next big thing. the way they handle my personal life and side projects is just ๐
@jayledev im not sure how grok bots keeps its sessions and manages its context, but I havent had any issues so far working up to 5 tickets in parallel from start to finish
my grok bot setup: one "Engineering Lead" bot is the only one i talk to. it hands work to an "Engineer" bot, sends the pr to a "Reviewer" bot when it's up, and so on. the lead always knows who's doing what, so no two bots grab the same ticket
For me, Ive set up an โEngineering Leadโ bot that handles all the orchestrating and is the only bot i talk to. It sends work to the โEngineerโ bot, when the PR is up, it sends the PR to the โReviewerโ bot and so on. This means the lead has an overview of whos doing what and you wont get any conflicts.