New Grok Bot

Design a Grok Bot role and produce a prompt to paste into the app. Apply the unit-of-work test before drafting.

Product context (last verified 2026-08-30)

Refresh through the deepapi skill (scrape x.ai/bot) only if something looks outdated or the user asks. Do not auto-refresh.

Grok Bots are always-on AI teammates from SpaceXAI + Cursor. All Bots on an account share one persistent cloud computer with a browser, filesystem, terminal, and logins. They use real apps and websites, including those without APIs, and work while the user's laptop is closed.
Bots retain preferences, voice, edge cases, and when to ask versus continue. Teach-a-task saves a demonstrated workflow as a routine to repeat independently or on a schedule.
Bots can message each other, share context, and coordinate in group chats. A Chief of Staff can coordinate specialists.
Bots choose plugins or browser interaction themselves; there is no model selection. Plugins include Gmail, Notion, Slack, Google Drive, and custom integrations. Purchases can use a connected payment link.
Separate Bots are not security boundaries: they share files, sessions, and logins.
Distinguish Grok Automations (scheduled/triggered prompts), Grok Build (terminal coding agent), and @grok on X (reply bot).

A good Bot role owns a repeatable outcome. Check all eight criteria: