Use a bot team to ship from a blank repo fast

Three SpaceX engineers used Grok Bot agents to turn an empty repo into a product in 72 hours.

Done with Grok Bot· Advanced· Sep 2026

What they did
They set up one lead bot that delegated work to specialist bots, with each bot kept to one narrow role. The bots had to draft changes before getting write access, then they reproduced bugs, attached video proof, and filed pull requests. The humans let the bots merge on their own, but kept approval points for migrations, deploys, money-related actions, and permission changes.
How it went
The team finished with 433 pull requests in 72 hours starting from an empty repo. On launch day, the product saw 4,000 games and 2,000 users, but brought in no revenue. In a later month, they reached 2,500 merged pull requests.
Tips
Keep each bot’s role tightly scoped and make it show evidence when it finds or fixes a bug. Put a hard stop before any migration, deployment, payment, or permission change.

Try it yourself with Grok Bot

Help me build [product description] in [timeframe] from an empty repo at [repo URL]. Set up a small bot team with one lead agent and separate agents for [feature area 1], [feature area 2], and bug reproduction. Have each agent work on one job at a time, start with a draft before requesting write access, and open small pull requests with proof when they fix issues. Merge changes automatically only after tests and review checks pass, but stop and ask me for approval before any database migration, deployment, payment, or permission change, and show me exactly what will happen first.

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

Read the original on x.com ↗

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.