Grok Bot ships its own code, and a SpaceX engineer sometimes reviews PRs after they land
A video describes Grok Bot splitting work across chief-of-staff and eng-lead bots that review each other's PRs, with an engineer sometimes reviewing only after code lands.
HOLY SH*T. GROK BOT NOW WRITES ITS OWN CODE, AND A SPACEXSI ENGINEER SOMETIMES READS IT ONLY AFTER IT GOES LIVE. "Sounds kind of scary to say, but sometimes I actually don't even look at the PR until after it's landed." That's Lauren Tan, 27:45 into the video. A PR is a code change. "Landed" means it's already shipped. How the bots build the app: → A Chief of Staff bot breaks a big project into phases → An Eng lead bot splits it further for the coding bots → Each one comes back with a PR, and other bots review it first → The codebase is built to be "agent friendly", so a lot of those PRs merge on their own People now sign this app into their email, calendar and Slack. The guide quoted below explains why any Bot can use a login you gave just one of them. Bots are writing the bot you hand your accounts to.
This post quotes another post: x.com/aleiahlock/status/2113965935946027159