@0xCodez
Post
SpaceXAI engineer, Lauren Tan:
"GrokBot is the most powerful agentic tool we have ever shipped, but only 1% of users use it correctly|
at SpaceXAI, I'm running a team of 15+ GrokBot agents. I have a Chief of Staff agent, 3 managers and 11 workers - that's the new engineering setup in 2026"
In a 1-hour talk, a SpaceXAI engineer reveals how to get 100% of every agentic tool you are using
worth more than a $500 agentic course on the internet
skip Netflix and watch today, it will change the way you use GrokBot forever, then read the article below
![]()
Video thumbnail from X post
Quoted post by Codez (@0xCodez) https://x.com/i/article/2089655442657910784
Explanation
The post is basically pointing at a real shift in AI-assisted software engineering, but wrapping it in fairly aggressive hype. Codez says Lauren Tan, an engineer working on Grok Bot at SpaceXAI, runs a hierarchy of 15+ coding agents—one “Chief of Staff,” several managers, and many workers—and presents this as “the new engineering setup in 2026.” The important part is not the literal org chart. It is the idea that the human stops interacting with one coding model at a time and instead builds a supervisory system that can decompose work, run many agents in parallel, check their outputs, and keep iterating without constant human attention.
Tan’s publicly documented workflow supports the underlying idea. She says she shipped about 1,000 PRs in a month using cloud agents, and describes using her own `pstack` framework plus `/goal`, `/loop`, and `/swarm` to let agents take work from task definition through implementation, verification, and shipping. She also uses automated routines to collect bugs, complaints, and feature ideas, so her own role increasingly becomes choosing what the “factory” should work on rather than writing each patch herself. ([LinkedIn][1])
The key thing to understand is that “15 agents” does not mean 15 independently intelligent software engineers chatting among themselves. An agent here is closer to a long-running model instance with tools, repository access, instructions, state, and a job. You might have one instance investigating a bug, another implementing a fix, another reviewing the diff, and another running tests. The “Chief of Staff” metaphor means a higher-level agent knows what jobs exist, starts or routes work to specialist agents, watches their state, and decides what needs another pass.
`pstack` is what makes this less like “launch 20 chats and pray.” It is a collection of explicit engineering playbooks and rules: reproduce before fixing, gather runtime evidence, keep changes small, run verification, use different workflows for bugs versus performance work versus features, and so on. Its stated purpose is specifically to make parallelism safe by making each individual agent’s work more constrained and verifiable. ([GitHub][2])
`/loop` and `/goal` solve another problem: ordinary coding agents tend to stop after producing an answer or one patch. A loop gives the system permission to wake back up, inspect whether the goal is actually satisfied, run another test or repair cycle, and continue for hours. Cloud execution means that can happen while the developer’s laptop is closed. Tan explicitly describes agents working 24/7 this way. ([LinkedIn][1])
The subtle point is that the scalability comes much more from the harness than from making the underlying model smarter. If an agent can declare victory whenever it feels like it, multiplying it by 20 gives you 20 unreliable workers. If completion is mechanically checked—tests pass, reproduction disappears, lint/type checks succeed, benchmarks improve, review criteria are met—then parallelism becomes useful. That is why Tan’s material emphasizes verification so heavily.
I would not take Codez’s exact “1% of users,” “15+ agents,” or the neat “Chief of Staff + 3 managers + 11 workers” hierarchy as established facts from Tan herself. The stronger first-party evidence is the broader claim: she is genuinely running large numbers of cloud coding agents, has built a formal workflow specifically for high-confidence parallelism, and reports dramatically higher PR throughput from doing so. ([aiidelist.com][3])
[1]: https://www.linkedin.com/posts/laurenelizabethtan_cloud-agents-and-cursor-harness-improvements-activity-7495972438262853632-bLQ5?utm_source=chatgpt.com "Cloud Agents and Cursor Harness Improvements · Cursor | Lauren Tan | 17 comments" [2]: https://github.com/sankalpsthakur/pstack?utm_source=chatgpt.com "GitHub - sankalpsthakur/pstack: Tracking mirror of cursor/plugins pstack (Lauren Tan). Product PRs go upstream. · GitHub" [3]: https://aiidelist.com/blog/lauren-tan-grok-bot-pstack-workflow?utm_source=chatgpt.com "Lauren Tan's Grok Bot Workflow: pstack & Cloud Agents"