GitHubWhat they did
Roshan Sadanani, Lauren Tan and Matt Palmer of the xAI Grok Bot team streamed a three-day build next to Dreamforce in San Francisco in September 2026, starting from nothing and pivoting from a pop-up restaurant idea to a game studio. Each Grok Bot had its own cloud computer and a narrow role: a chief-of-staff bot, implementer bots writing small pull requests, verifier bots that ran the game, clicked through it and fuzzed for bugs, and a playtester bot watching for green CI. Lauren's PStack skills drove the pipeline, with a swarm skill spawning Cursor cloud agents for QA. Merges were gated on reproduced bugs and attached proof. GitHub user unicodef1wn watched the stream and distilled the three days into rules, nine role playbooks, a failure log and an economics sheet.
How it went
The game, Thursday Arena, launched from a single X post at about 10am Pacific on day three. By end of day it had roughly 4,000 games, 6,000 public matches, 30,000 page views and 2,000 users, with about 8 percent of practice players signing in via X. Feedback was 71 percent bug reports and 16 percent praise. Revenue was zero; the ad auction was broken. The bot pipeline landed more than 100 PRs overnight and 433 in total, with 157 commits from one host. The failure log lists forty things that broke on air.
Worth knowing
This is a vendor team demonstrating its own product on stream, written up second-hand by a viewer from auto-captioned transcripts, so names and figures should be read as order-of-magnitude. The cost lessons are the transferable part: routines every 15 minutes and bots in group chats are where tokens go, browser-driven form filling costs more than an API path, and the team kept a human gate on deploys, migrations, money and permissions throughout.
Slack