Jon Shulkin gives Grok Bot an office, org chart, and sitcom cast

Why it matters

Agent fleets need a control layer that makes ownership and handoffs visible. Shulkin's mockup supplies one, while Grok Bot's shared-computer design leaves access control as the harder problem.

Jon Shulkin (@jon), a partner and co-president at Valor Equity Partners, has built a visual office for his Grok Bot software team, assigning each agent a desk, a job, and the identity of a character from NBC's "The Office."

Shulkin posted GrokBot Office v2 on X on Friday, August 28th. The interface depicts a Dunder Mifflin branch populated by agents named Michael, Pam, Jim, Dwight, Stanley, Phyllis, Angela, Kevin, Oscar, Kelly, Andy, Creed, and Darryl. During a software build, Shulkin says, the agents work together and move into the conference room without waiting for him to coordinate each handoff.

The screenshots are labeled as mockups, and Shulkin has not presented the office view as an official SpaceXAI feature. The underlying agent roster is real, according to his posts: he has described separate Grok Bots responsible for project management, active build sessions, the build console, code audits, intelligence retrieval, and GitHub deployment. Shulkin says the agents communicate through a shared channel and escalate questions to him by push notification.

The character sheet makes the division of labor explicit. Michael is the product manager, Pam handles chief-of-staff and reception duties, Jim manages active sessions, Dwight runs the console, Stanley owns the knowledge index, Oscar owns intelligence retrieval, Kelly fetches information, and Darryl manages GitHub deployments. Other characters are marked as "sitters," apparently serving as placeholders rather than active roles.

Shulkin says the Grok Bots generated the Dunder Mifflin setting with Grok Imagine. SpaceXAI released Imagine Image 2.0 on August 7th, advertising stronger instruction following, text rendering, and consistency across edits. The office mockup tests those capabilities on a scene where labels, character identity, room layout, and repeated visual elements matter.

An org chart for agents

The sitcom skin supplies a management interface for work that otherwise happens across chat threads, terminals, browser sessions, and status messages. A manager can see which role is active, where a task sits, and when several agents have convened around the same build. That visibility becomes increasingly useful as agent products encourage customers to run multiple workers at once.

SpaceXAI launched Grok Bot in beta on August 11th. Each named Bot keeps its own conversation and role-specific context while working through a persistent computer in the cloud. SpaceXAI expanded access on August 26th to SuperGrok, Cursor Pro, and all Cursor Teams plans, putting the product in front of a wider group of individual developers and small teams.

The official Grok Bot documentation describes a Bot as a persistent, named agent with a defined job. Users can place two to six Bots in a group conversation, direct work to specific agents, and let them send asynchronous messages to one another. Shulkin's office gives that coordination a literal floor plan.

The visual separation should not be confused with technical isolation. SpaceXAI's security documentation says every Bot belonging to one user shares the same cloud computer, including its files, browser sessions, and command-line credentials. The documentation explicitly warns customers against treating separate Bots as security boundaries. A character assigned to deployment and another assigned to research may have different instructions, but both can potentially reach the same logged-in services.

That constraint makes role design and approval rules important. SpaceXAI recommends holding external messages, purchases, deletions, permission changes, and production actions for human approval. Shulkin's labeled office can clarify ownership, but the controls governing what each agent may do still live beneath the floor plan.

An investor builds his own operating layer

Shulkin brings an operator's interest to the experiment. A Texas McCombs profile published earlier in 2026 identifies him as the manager of Valor Siren Ventures and the leader of Valor's Scale Group, which provides operational support to portfolio companies including SpaceX and xAI. He joined Valor in 1998 after beginning his career at Bain & Company and earned an accounting degree from the University of Texas at Austin.

That background explains the emphasis on named owners, audit roles, evidence, and deployment gates. Shulkin has described his broader system as a software factory rather than an open-ended coding chat. The agents receive standing responsibilities, pass work to one another, and surface decisions that require a person.

GrokBot Office v2 packages that structure in a familiar metaphor. The agents have titles. Their status is visible. The meeting room represents a coordinated build run. For once, the org chart may be easier to understand because none of the workers are human.