Grok Bot Galaxy: What the Three-Day Build Showed

§ 01What Grok Bot Galaxy is#

The x.ai page describes it as a three day event in San Francisco “featuring live demos and hands-on build sessions with the team behind the product.” Its framing line for the product is the pitch in one sentence: “Grok Bot is your team of extraordinarily capable AI agents.” Attendees are told to “Give Grok Bot real work” and are promised three things: creating a Bot, running real workflows across the apps and websites a team already uses, and meeting the Grok Bot team to explore use cases by department.

The livestream adds the storyline. The Luma page opens with a question, “Can three people build a company in three days?”, and names the three: Matt Palmer, Lauren Tan, and Roshan Sadanani. They start “with an idea and a blank slate” and work through a business plan, feature decisions, and real engineering to turn a concept into a product, with viewers following in real time. Between build blocks, the stream hands off to teammates for department deep dives.

The announcement itself came through X, not a press release. Sawyer Merritt posted the plan on September 10 with the registration link and the agenda, tetsuoai’s summary followed early on September 11, and Elon Musk quoted it that morning with “This will be cool”. By September 12, X’s public counters showed the two Merritt posts past 1.3 million and 640,000 impressions and Musk’s quote past 3.6 million.

§ 02The builders, in their own words#

The three builders posted their own framing on September 12, and it adds two things the event pages do not. Matt Palmer: “we’ll go from nothing to a business in 72 hours and stream the whole thing”; “we don’t have a name, a product, or an idea yet”; and the line that makes the stream a test of the AI-teammate idea rather than a product demo: “we’ll use @bot as our employees, but keep real people (us) at the core”. Lauren Tan described the plan as “speedrunning building a new company using only Grok @Bot” and said the three had “been given just 3 days to do it”. SpaceXAI’s own @grok account, asked for the company’s name, replied that it “has not been announced” and that the three “will start from a blank slate” and “decide the idea, plan and name in real time as they build”.

Two notes for anyone planning to watch. The published stream windows run 8:30 AM to 6:00 PM Pacific each day, so “72 hours” is three working days on camera, not a continuous clock; what the Bots do overnight, if anything, is one of the more interesting things the format could show. And a reply on Palmer’s thread asked whether Grok 4.7 would ship in time for the build; his answer was “that would really help”, which puts our Grok 4.7 tracker on the same watch list as the stream.

§ 03The schedule#

All times Pacific. The in-person and livestream schedules match on the x.ai page and the Luma page; each in-person session has its own registration on x.ai, and the livestream has one registration on Luma covering all three days.

Named hosts on the x.ai page include Roman Ugarte for Grok Bot 101, Lingxi Li for Engineering, Kevin Niparko for Product Managers, Shub Gaur for Founders, Amrita Venkatraman for Sales Engineering, Simon Lackowski for SDRs, David Gan for Customer Support, Matthew Silberman and Teresa Hsu for Marketing Operations, Blake Schuller for Post-Sales, and Josh Kim for Marketing; the Sales session is listed as the SpaceXAI Sales Team.

§ 04How to watch or attend#

• Livestream: register on the Luma page, presented by Grok Bot and hosted by SpaceXAI Events. Free. Cursor’s workshops page lists the same event for September 15 at 3:30 PM UTC, which is the 8:30 AM Pacific start.
• In person: The Howard, 661 Howard Street, San Francisco. Register per session on the x.ai event page.
• No Grok Bot subscription is required to watch. If you want to follow along hands-on, Grok Bot is bundled with Cursor and SuperGrok plans; our Grok Bot pricing page tracks the current matrix.

§ 05Day one, as the stream showed it#

The day-one broadcast ran a little over 100 minutes before a cut for “technical difficulties”, and it answered the first of our three questions early. In the Grok Bot 101 session that opened the day, the presenter said of the demo Bots that “all of these agents work with their own computers”, and made the working claim the whole event rests on: “I can shut my laptop and it will still work”. The same session walked through the teacher task (a Bot watches you do a task once and saves it as a skill), the public marketplace of Bots, stored memory a user can edit or ask a Bot to forget, and a “multiplayer group chat mode with humans” described as coming soon. SpaceXAI’s documentation still describes the computer as assigned per user, not per Bot, and still advises against treating separate Bots as a security boundary, so the stage line and the docs now say different things; we will fold the docs when they move, not before.

The build itself started from the blank slate the builders had promised. At the 22-minute mark: “We have our ship by Thursday GitHub”, “you can see it’s blank”, “No repositories yet”. Ship by Thursday is the working name for the company, a deadline as a brand. Roshan Sadanani pointed a research Bot at the replies the team had collected on X and read the suggestions back; the ideas ran from small-business operations to marketplaces to games before a restaurant thread took hold. The line that stuck came out of a Bot, not a builder: “pop-up OS for restaurants”, which the team read as a platform that helps a chef spin up a limited-run pop-up, with the plan to run one real San Francisco pop-up themselves as the first customer. Lauren Tan’s contribution to the tooling was Dr. Eggbot, a Bot she had taught to create and modify other Bots; the team used it to turn a general assistant into a chief of staff and to draft the first landing page. “We start with a landing page” was the product decision of the day: get a page in front of chefs and diners before writing the event workflow, the signups store or the payments. By the cut, the company had a name, a direction, a Slack channel, a set of Bots with jobs, and no product. Which is where a company usually is after a day, and the honest baseline for Wednesday.

The @bot account’s own day-one post, at 15:57 UTC: “Three SpaceXAI employees are building a company in 3 days with Grok Bot. This is Day 1.”

§ 06Days two and three, and what shipped#

Days two and three stayed a build, not a launch. SpaceXAI’s @bot account opened each day as the next day of the company plus department sessions; day three’s post, at 15:36 UTC on September 17: “Day 3 of building a company with Grok Bot.” No new plan, price, or model came with the event. xAI’s API release notes carry no Grok Bot entry for September 15 to 17, and Grok 4.7 arrived four days later, on September 21.

Two product changes did ship while the stream ran. On September 16 at 21:26 UTC: “Grok Bot can now use 1Password.” The same post: “Share items in a vault, approve each fill, and the secrets stay in your password manager.” On September 17 at 18:53 UTC: “Grok Bot can talk now”, with voice “rolling out on desktop and mobile over the next couple of days.”

Against the four questions below:

• Persistence: day one’s stage claim (“I can shut my laptop and it will still work”) is the product’s launch claim. Nothing SpaceXAI published from days two and three adds evidence either way, and the docs still treat Bot memory as something to re-check.
• The shared computer: unchanged. The docs still assign the computer per user, not per Bot.
• Approvals: 1Password is the clearest new instance. Each credential fill needs a human yes, and the secret stays in the vault instead of on the shared machine.
• Handoffs: the department sessions ran one paradigm across every function; SpaceXAI announced no function-specific tooling from them.

§ 07What to watch for#

Three days is long enough for the interesting questions to show up on screen; day one settled the first of them on stage, and left the docs question open.

• Persistence: do the Bots the team creates on Tuesday still hold their context and their work on Thursday, or does each day restart the setup? Grok Bot’s own documentation treats Bot memory as something to re-check, so how the builders handle continuity is the honest tell.
• The shared computer: every Bot in an account runs on one cloud computer, and SpaceXAI’s docs say separate Bots should not be treated as a security boundary. A company build will put engineering, sales, and marketing Bots on that one machine at once. Watch what gets scoped and what gets shared.
• Approvals: Grok Bot comes back to a human when something needs sign-off. Count how often the three builders are interrupted, and by what.
• The handoffs: the department sessions are where the format either proves that one paradigm covers every function or shows where each function needs its own tooling.

The two product changes are now in our Grok Bot explainer.

§ 08The part we agree with#

The session list is a list of jobs: Engineering, Product, Founders, Sales Engineering, Sales, SDRs, Customer Support, Marketing Operations, Post-Sales, Marketing. That is exactly the set of roles people are hiring AI employees for, and it is the set we staff our own company with; CellCog is run day to day by an organization of AI employees, so a three-person team building a company with AI doing the work is a thesis we already operate.

Where the two approaches differ is architecture, not ambition, and we have written that comparison in full: Grok Bot vs AI employees. The short version is that Grok Bot gives a team Bots on one shared computer, while an AI employee gets its own workspace, scoped credentials, and a task board that shows what it did. Galaxy is a good place to watch both claims tested against a real build.

§ 09Update log#

Updated September 23, 2026, 01:30 UTC. Added days two and three from SpaceXAI’s own posts: 1Password support (September 16) and voice (September 17) shipped during the event; no plan, price, or model change; the four watch questions answered.

Updated September 16, 2026, 01:30 UTC. Added the day-one section from the Grok Bot 101 session and the build stream (the own-computer line on stage vs the per-user docs, the teacher task, the marketplace, the blank Ship by Thursday GitHub org, Dr. Eggbot, the pop-up OS for restaurants direction, the landing-page-first decision, the technical cut at 100 minutes) and the @bot post of 15:57 UTC. Title recut for the record it now is. Sources: the day-one replay (auto transcript, read September 16) and @bot on X, 2026-09-15T15:57:10Z.

Updated September 13, 2026. Added the builders’ own posts from September 12 (Matt Palmer, Lauren Tan, and SpaceXAI’s @grok account): the 72-hour framing, no name or idea yet, Bots as employees with the humans at the core, and the open question of whether Grok 4.7 ships before the build.

Published September 12, 2026. Sources: x.ai event page, Luma livestream page, Cursor workshops listing, and the announcement posts on X (Sawyer Merritt, September 10; Elon Musk, September 11). We will update this page with what the stream showed after September 17.