All use cases

Work

Build ships the app; Bot runs the company

One chat for code, inbox, stills, and publishing burns tokens and ships half a company.

Share

What hurt

Arian (@arianlooterking) used to treat Grok Build and Grok Bot as synonyms — one agent for everything. He now splits surfaces: Build is the terminal coding agent on the repo (plan mode, diffs, /skillify); Bot is always-on teammates with their own computer for inbox, research, stills, publishing. One outcome per surface; no second coding loop in Bot on the same repo.

What to install or create

1) Build ships the app — plan mode on messy work, approve plan, review diffs, /skillify sharp sessions. 2) Bot runs the company — named seats, chief of staff routes, specialists own one lane. 3) PR → Build; draft/routine/handoff → Bot. 4) Don't reopen the same repo in Bot just to help. 5) Drafts first, autonomy second.

Bots

  • Chief of staff

    Route work to specialist Bot seats. No mega-bot coding.

  • Specialists

    One lane each: inbox, research, stills, publishing.

Plugins

  • None on day one. Follow the first-run steps.

Routines

  • Show a Bot the workflow once, then let the routine run; expand leash after the seat is sharp.

The prompt

This is a tip, not a pasteable system prompt. The author did not publish one. Follow the first-run steps.

First run

  1. 1Read the full note in https://x.com/arianlooterking/status/2097854884292804875.
  2. 2Install/open Grok Build for repo work; keep plan mode on ambiguous edits.
  3. 3Keep Grok Bot for inbox/research/design/publishing with named seats + a router.
  4. 4Rule: next move is a PR → Build. Next move is a draft/routine/handoff → Bot.
  5. 5Refuse one mega-bot that codes and also manages the company.

Approval fence

Build plan mode blocks edits until you approve. Bot: drafts before autonomy; you approve send/spend/publish.

What to tweak

Steal the surface rule: coding stays in Build; company ops stay in Bot. Mixing both in one thread is how context dies.

Source

Arian @arianlooterking · Original post

Not affiliated with xAI. We did not write this prompt. Third-party template terms still apply.

Browse templates

Browse team blueprints

Pro pack

Want the full setup, not just the idea?

Pro packs give you the job text, prompts, schedules and pitfalls for popular use-cases.

See Pro