'Chief of Staff' bot emerges, coordinating multiple Grok bots to prep a Pokémon stream

What came out

Wes Roth posted a short note on his X account saying, "Really happy with the new Grok bots," along with a single screenshot. The screen shows a chat window titled "Chief of Staff," with a sidebar on the left listing sub-bots named Pokémon Coach, Host, Player, Avatar, and Safety. In the conversation, the Chief of Staff bot asks which starter to lock in, settles on Bulbasaur, and then instructs the Host bot to "switch to hype mode." It also reports to the Coach bot that "the runtime is partially ready — the first dry run will begin once the loop runner and emulator bridge are in place." A panel on the right explains that "a routine is a task this agent repeats on a scheduled basis," accompanied by a "Create Routine" button.

What this means

Grok bots is an agentic feature that xAI launched in early beta on August 11. It's available to Grok Heavy, Grok Ultra, and Grok Team Premium subscribers, and lets users design and run their own bots, which then operate on a dedicated cloud machine around the clock to handle actual tasks. Saved routines run automatically on a schedule, and bots can also work together. The feature supports macOS, Windows, iOS, and Linux, with Android support reportedly in the works.

A day after launch, on August 12, an operator of an AI news account first revealed a setup using nine Grok bots to run a one-person business — handling morning briefings, scheduling, and email organization. What Wes Roth showed is different in character. Rather than acting as a work assistant, multiple bots were deployed for an entertainment-oriented project: running a Pokémon game session. The Chief of Staff issues top-level instructions like a manager, while Coach, Host, Player, Avatar, and Safety each handle a distinct role — game-progress decisions, broadcast hype, controls, character representation, and safety checks. The structure, where several bots function together like a single "team," echoes the pattern seen in the earlier one-person business case.

What changes as a result

Just two days after Grok bots launched, examples have emerged covering both work automation and gaming-content automation. Both cases so far are individual screenshots shared as informal trials, but the trend of experimentation spreading beyond coding or office support into areas like streaming content production is clear. It's not possible to tell from this post alone whether the project actually went live as a broadcast or how the dry run turned out. Still, the pattern of splitting multiple bots by role and having one top-level bot coordinate them appears to be emerging as a recurring usage pattern among Grok bots users.