What Is Grok Bot? Access, Pricing, Setup & How It Works (2026)

Grok Bot is an early-beta agent product from xAI. It launched on August 11, 2026 as a way to hand ongoing work to persistent AI teammates. Each Bot can use connected tools, work in a shared cloud computer, remember the context of its job, and continue after you step away.

The important distinction is that Grok Bot is a product, not a model name and not an API key. You do not select "grok-bot" as a model in an API request. If you want to call Grok from your own application, start with the Grok API Key complete guide or the xAI provider page.

Grok Bot is built for delegated work: research a topic, monitor an inbox, update a document, operate a website, or repeat a tested process on a schedule. Because it can act on real systems, it also needs tighter permissions and review rules than an ordinary chatbot.

Grok Chat answers you inside grok.com or the Grok apps. The Grok API lets developers send requests to Grok models from code. Grok Bot sits one level higher: it is an agent workspace that can plan a multi-step job, use plugins or a browser, and return when it needs approval.

A Grok Bot subscription does not replace an xAI developer account or automatically give your application an API key. Conversely, an xAI API key is not the credential used to sign in to the Grok Bot desktop app. The two products belong to the same ecosystem but solve different problems.

Grok Bot is not currently sold as a standalone subscription. Official plan documentation checked on September 3, 2026 lists access through paid Cursor plans, Cursor Teams, individual SuperGrok plans, and X Premium+. SuperGrok or X access is linked to the Cursor account that will own the Bot usage.

Included usage resets weekly. If that allowance runs out, work can continue against shared on-demand spend when the account has it enabled. The free trial is usage credit rather than unlimited access for a fixed period, although a seven-day window also applies. Long agent runs consume more steps and tokens, so one large task can use a substantial share of the trial.

The table shows entry prices displayed on the official Grok Bot page on September 3, 2026. Taxes, billing cycles, regional prices and higher tiers can differ. The official pages describe weekly usage by relative level rather than publishing a fixed number of steps or tokens, so check the in-app plan screen before paying.

Use the official Grok Bot download page to get the app. Current setup documentation lists desktop builds for macOS, Windows and Linux. Windows offers x64 and Arm64 installers; Linux releases include deb, rpm and AppImage formats.

The mobile app currently supports iPhone with iOS 18 or later and Android phones with Android 9 or later. It is designed for phones rather than iPad. Mobile can start work, answer questions and approve steps, but editing routine schedules and some teach-by-demonstration workflows still require the desktop app.

Open the app and sign in with the Cursor account that owns or will receive the eligible usage. If you are linking SuperGrok or X Premium+, verify the Cursor account first: official documentation says that link cannot be moved to another Cursor account later.

Create one narrowly defined Bot instead of a catch-all assistant. Give it a short name, one job, the sources it may use, the output you expect, and the situations where it must stop for approval. Start with a reversible task before connecting sensitive systems.

If an eligible plan does not appear, first confirm that Grok Bot is signed in to the Cursor account that owns the plan or received the linked usage. A SuperGrok or X Premium+ link is permanent and cannot be moved to another Cursor account, so do not repeat the linking flow with a second account.

If a plugin will not authorize, remove it, add it again and finish the provider login in the browser. If the desktop app hangs, fully quit it before reopening; closing the window may leave the process running. The official troubleshooting guide lists current recovery steps.

When contacting support, include the Cursor account email, operating system, Grok Bot version, Bot name, exact error text or screenshot, and the steps already tried. Do not include passwords, one-time codes or API keys.

Bots share a computer in the cloud. They can operate websites through a browser and use connected plugins for supported services. If a page requires a password, passkey, two-factor code or CAPTCHA, the Bot asks you to take over. You enter the credential yourself and then return control.

A skill records a process the Bot has learned, while a routine runs a repeatable job on a schedule. Test the process manually first. A routine will faithfully repeat a bad workflow too, so check sources, permissions and output before letting it run unattended.

Browser sessions can persist on the shared computer. That is convenient, but it also means another Bot may be able to use the same signed-in session when appropriate. Separate high-risk work, grant the smallest useful permissions, and remove connections you no longer need.

The best first job has a clear finish line and produces something you can inspect. Research with source links, draft preparation, issue triage, calendar checks and recurring status reports are easier to verify than an open-ended instruction such as "manage my business."

For software work, a Bot can inspect a repository, reproduce a bug, draft a patch or monitor an issue queue. Keep production deployment, account deletion, financial transactions and irreversible changes behind explicit approval until you understand how the Bot behaves.

Grok Bot is easiest to justify when you already pay for an eligible plan and have repeatable work that crosses websites or apps. The free trial is enough to test one tightly scoped workflow, but it is not proof that every long-running automation will be economical.

It is less compelling if you only need occasional chat or coding help, cannot store the work in a cloud environment, or expect an agent to make irreversible decisions without supervision. Treat the beta as a workflow test: compare the time saved with the review time and usage consumed before upgrading for Grok Bot alone.

The X connector lets a Bot search posts, read a timeline, check mentions, collect current discussions and manage bookmarks. In its August 29 integration announcement, xAI said it can create an X developer account during connection when the user does not already have one. Paid Grok Bot users also receive introductory X API credits, subject to the current program terms.

Connect X from the Grok Bot plugin settings, complete authorization in the browser, and start with a read-only research task. Review the requested permissions before allowing posting, messaging or bookmark changes.

Grok Bot requires cloud data storage. Accounts using Cursor Legacy Privacy Mode must switch to a supported data setting before the product can start. Review the official security and privacy controls before assigning confidential client data, private repositories or regulated information.

Never paste an API key, password or recovery code into the Bot conversation or an ordinary file. Use the takeover flow for interactive login and the secure secret card for credentials needed by tools. Rotate a secret immediately if it appears in chat, logs, screenshots or a repository.

The product is still in beta. Keep destructive actions behind approval, retain backups, and inspect citations or changed files before accepting a result. Autonomy saves time only when the review boundary is clear.