The alpha, twice a week
That was 5 min instead of 45 min.
Get the best new moments in your inbox every Wednesday and Saturday. It's free.
Check your inbox
We sent a link to your address. Click it to finish signing up. Not there in a minute? Look in spam.
or
Behind the Craft · 5 min instead of 45 min · Sep 27, 2026
An eng lead bot that only delegates lets one person run agent swarms
With Peng Zheng & Lauren Tan

Peter YangHost · Host, Behind the Craft
Led product at Roblox, Reddit, Twitch and Meta for 10+ years.
About this segment
Lauren has an eng lead bot that never does work itself and only delegates to engineer bots, which spawn cloud agents. Her agent-friendly codebase means PRs sometimes auto-merge before she reads them.
From “We Built Grok Bot. Here Are Our 14 Best Bots | Peng Zheng & Lauren Tan”, Sep 27, 2026. Watch the full episode
Takeaways
- Tell the eng lead bot to never work itself, only break down and delegate
- Engineer bots spawn cloud agents, so you can pick models by task
- An agent-friendly codebase lets PRs land before you review them
In this episode
Full episode- 39:29Build trust in a bot by turning observed runs into skills2:57
25:20An eng lead bot that only delegates lets one person run agent swarms4:44
- 6:19Persistent named bots beat disposable chat sessions3:10Up next
Transcript
Transcribed by machine (Whisper) from the episode’s audio, so a word may be off here and there.
- 25:26
So basically, each one works on a ticket or something? Or how do you dedicate responsibility to? Yeah, so I actually mostly talk to my chief of staff, and then my chief of staff talks to the eng lead. But I set these bots, these engineer bots up with Dr. Aikbon, of course. But one of the things I kind of drove, I told Dr. Agua to do is to make sure that the end leads job is really to, you know, break down tasks into smaller pieces and delegate and supervise other bots rather than do work on its own.
- 26:01
So you can see that the description that basically it has like even the bot IDs in there, but it tells it to, you know, never do work on your own. and always delegate to those four bots and then it will it basically does that and a lot of the work as well is done through cloud agents so for example one of these bots will in order to do the work they will like create a cloud agent and then you can you know open that in Cursor or on the web, but yeah, this allows me to essentially make use of different models depending on the type of task, because some tasks are more straightforward and I just want really fast speed. Other tasks maybe require a bit more planning and a bit more reasoning, and then I'll might adjust the reasoning level. So cloud agents in GrokBot give me a lot of very granular control,
- 27:03
i guess um and also ensures that you know like my bot kind of stays i kind of treat each of these engineers as more like like they're like they're supervisors in a way uh we have like so we have like the engine that manages them but then they themselves try not to do work on their own uh so they always spawn um cloud agents for me so just kind of like passing orchestrate yeah they do all the message passing, but it lets me orchestrate really massive agent swarms.
- 27:34
If I need to tackle a very big project, I can just talk to my chief of staff and say, break this down. I have a giant project. Maybe let's do some planning first in an ocean doc. And then it will start thinking about the phases of the work that it needs to do. And then it'll delegate it all to the engine lead and we'll then break it down even further and have the bots kind of work on that. Okay, then each one will come back with like a PR and stuff.
- 28:00
the bots will review it first is that kind of how it works yeah essentially uh although for me yeah uh one of the things i've done a lot uh that i talk about a lot as well on x is the idea that like for example the graphbot code base we've tried to make it very how do i say uh make it very agent friendly the architecture of the code base is very agent friendly so a lot of times it actually just lets me auto-merge my PRs. So it sounds kind of scary to say, but sometimes I actually don't even look at the PR until after it's landed. And then I'm like, oh, okay, yeah, that looks good. Got it. Wow. Okay. So you have like a software factory? Is that the buzzword?
- 28:47
I like to call it the Michelin kitchen because I think software factory, yeah. I like to call it michelin kitchen because to me michelin kitchen you see like there's this uh when you when you think about a michelin starred kitchen right you think about the quality right and the craft that goes into making those uh you know the the product right which is a dish or a meal uh and there's still scale involved right like you know a kitchen a restaurant might have you know 50 seats or 100 seats uh so you need to be able to like produce quality at scale so that's the aspirational vision i have is like i want to set a michelin kitchen not just like you know a factory which uh interestingly i think a lot of people's like when you say factory they have this connotation like oh you know it's just like it's mass manufactured it's like a sloth is like low
- 29:40
quality yeah but i always try to aspire to do both right like how do we get quality at scale So yeah, this is a lot of the work I've done on Pstack and using GrokBot together with it is in that line of how do we create that Michelin kitchen. Yeah, you should make a concierge bar or something that talks like, hey, we curate