Grok Bot Is a Cloud Teammate, Not a Chat Window
You assign work that can finish inside your tools and keep running after you close the lid. Short Q&A, pure repo changes, and one-off desktop cleanup belong elsewhere.
xAI's official line: bots are teammates that do real work, sign in to your tools, use them like you, and come back with finished work — pulling you in only for judgment calls.xai-bot The difference from a chat window is not tone. It is whether the work continues after you close the lid.
After reading, you should be able to answer:
- What kind of work belongs on Grok Bot?
- Which three kinds should you not send it?
- What extra duty comes with calling it a teammate?
Fits: work that should continue while you are away
Inbox triage on a rule, watching one class of sources and returning a brief, finishing a job with stops across apps you have already signed into. Shared traits: the process runs on a cloud computer; the artifact is a file, a draft, or an item waiting for you; it should continue after you close the lid until it hits a judgment call. The first job is still one closed loop. See pick the first job.
Does not fit
- Short Q&A. That is chat Grok, not a bot.
- Pure repo coding. See Codex. Officially, code work stays on the coding side; the bot is not a repo plugin.
- One-off cleanup that lives on your desktop and finishes while you watch. See WorkBuddy. Office document cowork: Doubao Work.
Teammate means a role and a stop
A teammate has a duty, sources, a judgment bar, and a report format. Without those four, you hired someone who does everything — which is no one. Isolation is at the account layer, not “each bot is a security wall.” That official judgment shows up in every later article in this chapter.