Bottom line: Grok Bot is a persistent AI teammate, Grok Automations is a scheduler and trigger system inside regular Grok, and Grok Build is a coding agent for the terminal. They share the Grok name and some agent-style capabilities, but they are built for different people, interfaces and kinds of work.
If you remember only one line, make it this: Bot = teammate. Automations = trigger. Build = coding agent.
Research note: This is a documentation-only comparison, checked on August 11, 2026. Kingy.ai did not conduct hands-on product testing for this article. Availability and plan rules can change quickly.
Grok Bot vs. Grok Automations vs. Grok Build: Quick Comparison
| What to compare | Grok Bot | Grok Automations | Grok Build |
|---|---|---|---|
| Primary purpose | Delegate multi-step work to persistent, named AI teammates | Run a saved Grok job on a schedule or email trigger | Plan, edit, test and review software from a codebase |
| Typical users | Operators, sales, recruiting, finance, support and knowledge-work teams | Any Grok user who wants recurring briefs, reminders, monitoring or inbox triage | Developers, engineering teams and people scripting agentic coding work |
| Autonomy | Broad and persistent. Works in the background, retains role context, uses apps and can coordinate with other Bots | Bounded and repeatable. Each run is a fresh request using the same instructions and current data | Deep but code-focused. Can inspect files, edit code, run commands and use subagents, with approval controls |
| Main interfaces | Dedicated macOS and Windows desktop app; iPhone companion app; persistent cloud computer | grok.com and the regular Grok apps on iOS and Android | Interactive terminal UI, headless CLI, scripts and Agent Client Protocol integrations |
| Availability | Eligible plans currently include SuperGrok Heavy, Cursor Ultra and Cursor Teams Premium; team access is rolling out | Scheduled automations are available to everyone; email triggers require SuperGrok | Current product page says free to try; installs on macOS, Linux/WSL and Windows, with account or API-key authentication |
| Best use cases | Cross-app research, reconciliation, preparation and repeatable operational roles | Morning briefs, weekly summaries, reminders, monitoring and email-triggered alerts | Repository exploration, feature work, debugging, testing, refactoring, code review and CI scripting |
The biggest terminology trap is Grok Bot. In this article, it means the new product documented by xAI as a persistent AI teammate. It does not mean the familiar @grok account that replies to posts on X.
What Is Grok Bot?
Grok Bot is the closest of the three products to hiring a digital teammate. xAI defines a Bot as one persistent, named agent. You message it with a job, context and boundaries, and it can continue working on a cloud computer after you close the app.
That cloud computer is the key distinction. It includes a browser, filesystem and terminal, so a Bot can work inside websites and desktop-style tools rather than stopping at a chat draft. It can also use connectors or Model Context Protocol integrations when a structured connection is available.
Grok Bot is also designed around durable roles. A named Bot can keep preferences, files, browser sessions and role-specific context across turns. Multiple Bots can exchange messages, share context and hand work to one another. A process demonstrated once can be saved as a skill or routine and run again on demand or on a schedule.
This makes Grok Bot a strong fit when the job crosses several systems. xAI’s own examples include sales research, talent scouting, expense reconciliation, paid-media monitoring, account-health analysis, bug reproduction and a chief-of-staff digest. The common thread is not a single prompt. It is ownership of a repeatable outcome.
Who should choose Grok Bot?
- You need work completed across several logged-in apps or websites.
- You want the same named agent to build useful context over time.
- The workflow benefits from background work, handoffs or several specialized agents.
- You need a human approval point before consequential actions such as sending, publishing, deleting or changing production systems.
There is an important security detail: all of a user’s Bots share one account-scoped cloud computer, including its files, browser sessions and app logins. Separate Bots are therefore not separate security boundaries.
At the time of checking, Grok Bot requires an eligible plan—SuperGrok Heavy, Cursor Ultra or Cursor Teams Premium—and uses Cursor authentication. The desktop app supports macOS and Windows, while the mobile companion supports iPhone on iOS 18 or later. Linux desktop, Android and iPad are not supported at initial launch.
What Are Grok Automations?
Grok Automations turns a Grok prompt into a recurring or event-driven job. You describe the task, optionally attach files and add connectors or skills, choose a mode, and decide when it should run.
Schedules can run once, daily, on weekdays, weekly, monthly or yearly. An email trigger can also launch a run when a new message matches sender, recipient or subject filters. Every run opens a full Grok conversation, saves it to run history and can report back by email, app notification, both or neither.
The crucial phrase in xAI’s documentation is “every run is a fresh request.” The automation reuses the same instructions but works with current data. That is different from Grok Bot’s persistent teammate identity, durable computer state and accumulated role context.
Who should choose Grok Automations?
- You can describe the job as one stable prompt.
- The work should happen at a known time or when a matching email arrives.
- You mainly need a result, alert or summary—not a persistent agent role.
- You want the simplest path from ordinary Grok chat to recurring work.
Good examples include an 8 a.m. news brief, a Monday pipeline summary, a monthly reminder, a daily scan for pricing changes or an alert when an important customer email arrives. You can create an automation from the Automations page, a template or directly from chat.
Automations are available on grok.com and in the standard Grok apps for iOS and Android. Scheduled jobs are available to everyone, while email triggers are included with SuperGrok.
What Is Grok Build?
Grok Build is xAI’s terminal-native coding agent. It opens inside a project, understands the repository, reads and edits files, runs commands, shows diffs and helps move a software task from plan to tested change.
Its main interface is an interactive terminal UI, but the agent can also run headlessly for scripts and CI jobs or connect to other applications through the Agent Client Protocol. Grok Build supports skills, plugins, hooks, MCP servers, project instructions and specialized subagents that can work in parallel.
Autonomy is deep but domain-specific. Grok Build can take substantial action inside a repository and local development environment. Plan mode can block edits until the user approves the approach, and permission settings govern tool execution. That is very different from Grok Automations’ scheduled chat runs and Grok Bot’s cross-application cloud workspace.
Who should choose Grok Build?
- Your source repository is the center of the task.
- You want an agent to implement, test and review changes rather than only suggest code.
- You need a terminal workflow, headless execution or CI integration.
- You want extensibility through skills, plugins, hooks, subagents or MCP servers.
The current Grok Build page says it is available to try for free and provides installers for macOS, Linux/WSL and Windows. Users can authenticate with a Grok account or an xAI API key. xAI also open-sourced the Grok Build agent harness and terminal UI in July 2026, allowing developers to inspect the implementation, compile it and point it at supported custom models.
For more developer context, see Kingy.ai’s earlier Grok Build launch analysis and the broader State of AI Coding Tools 2026.
Where the Three Products Overlap
The overlap is real, which is why the names feel confusing. Grok Bot can run routines. Grok Automations can use connectors and skills. Grok Build can run headlessly inside scripts and automated systems. All three can therefore perform work without a person typing every next step.
But the execution environment decides which one fits:
- If the job lives across SaaS tools, websites and a shared cloud desktop, choose Grok Bot.
- If the job is one reusable prompt tied to a time or email event, choose Grok Automations.
- If the job lives in a repository and ends in code, tests or a reviewed diff, choose Grok Build.
One product can imitate part of another’s job, but that does not make it the best default. You could schedule a headless Grok Build command, yet it would still lack the consumer-friendly Automations page and notification history. A Grok Bot has a terminal, yet Build has the engineering-specific plan, diff, repository and development-tool workflow. An Automation can query connected services, yet it does not become a persistent named teammate with its own durable computer environment.
Which Grok Product Should You Use?
| Your actual need | Best fit | Why |
|---|---|---|
| “Give this role to an AI teammate and let it work across our tools.” | Grok Bot | Persistent identity, cloud computer, background work and multi-Bot collaboration |
| “Run this same brief every morning.” | Grok Automations | Fastest schedule-based setup inside regular Grok |
| “When this kind of email arrives, analyze it and alert me.” | Grok Automations | Native email triggers, filters and notification options |
| “Research across several logged-in systems and prepare a review package.” | Grok Bot | Works across websites, apps, files and connectors on a persistent computer |
| “Implement this feature and run the tests.” | Grok Build | Repository-aware editing, terminal execution and diff review |
| “Put an AI coding step inside a script or CI pipeline.” | Grok Build | Headless output modes and ACP integration |
The Availability Difference Matters
The three products are not simply Free, Pro and Enterprise versions of one feature. Their access paths are separate.
Grok Automations has the broadest consumer reach because scheduled jobs are available to everyone in the web and mobile Grok apps. Grok Build is currently free to try, although its May 2026 launch announcement originally described an early beta for SuperGrok and X Premium Plus subscribers. The current product page is the better source for present access. Grok Bot is the most restricted: its launch documentation lists specific SuperGrok and Cursor plans, plus a limited platform set and a team rollout still in progress.
That packaging can change. Check the linked official access and pricing pages before buying a subscription for one particular feature. For a broader view of the underlying assistant, see Kingy.ai’s Grok tool profile and Grok 4.5 workplace-AI analysis.
Final Verdict
xAI is not selling three versions of the same agent. It is building three different layers of automation around Grok.
- Grok Bot is the ambitious general-purpose option: a persistent AI teammate that can operate across tools and keep working in the cloud.
- Grok Automations is the simple repeatability layer: one saved instruction, a schedule or trigger, and a result delivered back to you.
- Grok Build is the specialist: a coding agent designed around repositories, terminals, diffs, tests and software delivery.
For most readers, the choice is straightforward once the job is named correctly. Choose the teammate for cross-tool ownership, the trigger for recurring chat work, and the coding agent when the deliverable is software.
Official Sources and Verification Notes
| Official source | Used for |
|---|---|
| Grok Bot overview | Product definition, cloud computer, persistence, collaboration and shared-computer model |
| Grok Bot get started and FAQ | Eligible plans, authentication, supported platforms, background work and security boundaries |
| Grok Bot use cases | Documented roles and approval-oriented workflow examples |
| Automations in Grok | Schedules, email triggers, fresh-run behavior, notifications, interfaces and availability |
| Grok Build documentation | Terminal UI, headless mode, ACP, installation and API-key authentication |
| Grok Build product page | Current free-trial availability and core development features |
| Grok Build open-source announcement | Open-source harness, local-first use and extensibility |
FAQ
Is Grok Bot the same as @grok on X?
No. In xAI’s current product documentation, Grok Bot is a dedicated app for persistent, named AI teammates that work on a cloud computer. The @grok account on X is a separate in-feed reply experience.
Can Grok Automations use connected apps?
Yes. An automation can include connectors and skills in its saved instructions. Email-triggered runs can also use the matching message as context. It still runs as a fresh request each time rather than as a persistent named teammate.
Is Grok Build a model or an app?
Grok Build is a coding-agent application and command-line interface powered by a Grok model. The underlying model can also be accessed separately through the xAI API, but using the model alone does not reproduce the full Build harness, tools and terminal workflow.
Which Grok product is the most autonomous?
Grok Bot has the broadest general-purpose autonomy because it is persistent, works in the background and can coordinate across tools and other Bots. Grok Build can be more autonomous inside a software repository. Grok Automations is intentionally narrower and more predictable.
Which Grok option is free?
xAI says scheduled Grok Automations are available to everyone and that Grok Build is available to try for free. Email triggers require SuperGrok. Grok Bot currently requires one of the eligible plans listed in its documentation.