GROK BOT

Every Grok Bot works on a persistent cloud computer with browser and terminal access, and that single primitive explains everything else about the product. Here is why own-computer beats chat drafts, API integrations, and session-scoped agents.

Grok Bot ships controls over agents rather than controls by agents: approval gates, a chief-of-staff structure, and escalation learning stand in for a settings page. Here is how that oversight model works, and the control questions xAI has not answered publicly.

Grok Bot ships four primitives that compose - a text thread, its own cloud computer, a chief of staff over specialist Bots, and show-it-once routines - and deliberately nothing else. That restraint is the product: you message a coworker instead of configuring an automation platform.

Grok Bot's routines flip the automation playbook: do the job once while a Bot follows along, correct it in plain language, then let the Bot own the schedule. Here is how the mechanic works, where it fits, and how approval gates keep it safe.