Your Grok cheat sheet.

Chat lives on grok.com, X, and the consumer Grok apps. Build is the terminal agent at x.ai/build. Bot is its own desktop and iOS app: named teammates, a shared cloud VM, plugins, and routines. A grok.me app published from chat is not the Build CLI. Bot usage is a separate meter from the SuperGrok weekly pool that covers Chat, Imagine, Voice, and Build.

• Do not treat three Bots as three isolated machines.
• Hiding a Bot from the sidebar does not pause its routines.

Individual sticker prices live on x.ai/pricing and change there. Free, SuperGrok, and SuperGrok Plus are the cards with printed monthly amounts. Lite, Heavy, Business, and Enterprise appear in the comparison matrix. If you hold both a Cursor plan and a SuperGrok plan, Bot docs say Grok Bot uses whichever has more usage. X Premium+ is an X product; grok.com billing covers SuperGrok bought on grok.com.

• The dual-list mismatch is documented. It is not a METAGROK call.
• Do not invent a price from this page.

A chat message uses little compute. A high-quality video or a long coding task uses far more. The Usage tab shows percentage used, the breakdown by product, the weekly reset time, and any Extra Usage Credits. When the included week is gone, paid features pause; free-tier Chat and Voice keep a separate schedule. Extra Credits cost more per action than included weekly usage.

• Bot sand-tokens are not this SuperGrok bar.
• Sign in with the login that owns the subscription or the meter looks wrong.

Read the live Free, SuperGrok, and SuperGrok Plus cards, then the Image generation and Video generation rows in the matrix. SuperGrok Plus lists 1080p video creation. A remaining weekly percentage does not guarantee more 720p seconds — the 720p cap can trip first. Free and paid Imagine stills keep the Grok watermark.

• Hitting a limit looks like a stall or upgrade prompt, not “Imagine is gone.”
• Do not invent prices from this page. Open the live cards.

Put standing project rules in AGENTS.md or .grok/rules/. Point at files with @. Say what must not change. Say the check that proves done. grok inspect lists the rules files that loaded. “Make it better” has no finish line. Consumer Projects on grok.com are a different product from Build project rules.

• Short, specific rules are followed more reliably than long ones.
• Skip /plan for a one-path rename or a read-only look at the tree.

grok -w starts a worktree under ~/.grok/worktrees/. It copies current HEAD, including uncommitted changes, unless you pass --ref. Worktrees persist until you remove them. Subagents can request worktree isolation when the parent splits parallel work. Bot’s cloud computer is a different product from a Build worktree.

• Two agents on one dirty working copy will collide.
• Clean up with grok worktree rm or grok worktree gc.

Official FAQ: durable teammates on a cloud VM with browser, filesystem, and terminal. Create up to 50 Bots and group chats combined. Each Bot keeps its own conversation and role. Files, browser sessions, and app logins are shared so handoffs work. Treat any login or file on that computer as available to every Bot on the account.

• Hiding a Bot from the sidebar does not pause its routines.
• Deleting a Bot can leave shared files and logins behind.

Take over the computer for the blocked step, then tell the Bot to continue. Do not paste passwords or one-time codes into chat. A homepage “Approval needed” badge can stick after the Auto-review card expires. If the queue is empty, a short follow-up in that chat usually clears the stale tile. A live card still needs Approve or Deny.

• Hiding a Bot does not clear its approval state.
• Use the secure secret request when a connector offers one.

Save the method from a finished thread, or use Teach a task when the control is present (ten-minute cap, gradual rollout). A useful skill states inputs, steps, output, verification, and what needs approval. A routine names the owning Bot, cadence, timezone, finish line, and approval gates. Test run does real work.

• A Bot can own 50 routines. Deleting the Bot deletes its routines.
• Broad event listeners burn usage and act on noise.

Open Settings → Plugins, add the connector, finish browser auth, then type @ to attach it. Computer use operates the Bot’s screen. One Bot can run one computer-use task on its screen at a time. Connectors, files, and coordination can still run in parallel across Bots. Browse the live catalog; do not invent connector names.

• Sessions on the shared computer are available to every Bot on the account.
• If the page refuses automated control, take over or change approach.

Anyone with the link can see identity, description, skills, and routines. Adding a shared Bot creates a copy on their account. Team “same roster, live memory, separate chats” is not the product today — copies drift as soon as either side edits. Templates exist. Deeper collaboration is in progress with no ETA.

• The recipient needs the Grok Bot app to finish adding it.
• One owner account is account sharing, not multiplayer.

Bot background routines keep going with the laptop closed. Confirm the owning Bot, timezone, inputs, expected result, and what to do when a source is missing. In Build, type while a turn runs to queue the next prompt; /queue lists what is waiting. A scheduled prompt that says “keep an eye on things” will wander.

• Hiding a Bot does not pause routines.
• /queue is not /tasks or /loop.

Split when the next step does not need the previous answer. In Build, subagents return a summary to the parent; worktrees keep Git checkouts apart. In Bot, two named Bots still share one computer — isolate by Bot description and disk folder, not by hoping for a vault. Two chats on one Bot are still one teammate.

• Status-beat routines on a shared agent id leak projects.
• Do not treat a second Bot as a security boundary for logins.

If every message fails while the computer pane still shows a desktop, and Reset mentions a partial state, stop clicking Reset. That class is backend recovery, not a prompt rewrite. Distinct from usage exhaustion and a stale client session that still prints firewall wording. Collect version, OS, and exact error text before you file.

• Stale session can look like a dead computer.
• Hammering Reset does not clear a backend partial state.