usebot.net

Guide

What is Grok Bot?

A current, source-linked explanation of Grok Bot: apps, plans, skills, routines, plugins, approvals, the box computer, and how it differs from Grok chat.

Updated 8/27/2026

On this page · 5
  1. What Grok Bot can do
  2. The main building blocks
  3. What Grok Bot is not
  4. A sensible first path
  5. Sources and verification

Grok Bot is a task-oriented AI assistant designed for work that can extend beyond a single chat reply. Its product surface includes desktop and iPhone apps, reusable skills, scheduled or event-triggered routines, plugins for authorized services, approvals, and a computer environment often called the box.

It is not simply another name for every Grok experience. The general chat product on grok.com and the dedicated Grok Bot workflow experience have different interfaces and expectations. This distinction matters when you search for a download, plan, mobile requirement, plugin, or troubleshooting step.

What Grok Bot can do

The useful mental model is “assistant plus workflow system.” Depending on your platform, plan, permissions, and connected services, Grok Bot can help you:

  • Research and summarize material
  • Draft documents and structured artifacts
  • Work with files and tools in its computer environment
  • Reuse a reliable method as a skill
  • Run work on a schedule or supported event as a routine
  • Read or act through an authorized plugin
  • Pause for approval before sensitive or consequential actions

The surrounding controls matter as much as answer quality. A routine with unclear inputs will repeat uncertainty; a plugin with broad access increases risk; an approval clicked without reading defeats the safety boundary.

The main building blocks

Apps and platforms

Official documentation currently provides Grok Bot desktop builds for macOS on Apple silicon and Intel, plus Windows on x64 and Arm64. The iPhone app requires iOS 18 or later. iPad, Android, and Linux desktop support are not currently listed for the dedicated app. Check your device with the platform checker.

Plans and account linking

Access is currently included with paid Cursor individual plans and Cursor Teams. Eligible individual SuperGrok subscriptions can be linked to Cursor; not every SuperGrok tier or organization plan uses that path. Current pricing and quotas should always be confirmed on the first-party plan page. Use the plan finder for the documented access route.

Skills

A skill stores reusable guidance or a repeatable method. It is useful when the same standards, steps, or output format should apply across tasks. Keep changing details—such as date range, client, or source file—outside the stable skill when possible.

Routines

A routine runs work on a schedule or supported event. Good routines define their inputs, timezone, missing-data behavior, output contract, and review gate. Test a task manually before scheduling it. Official documentation currently describes up to 50 routines and access to 20 recent run records; limits can change.

Plugins

Plugins connect external services you authorize. Cursor currently documents Gmail, Notion, and Slack. Availability, provider scopes, and team-administrator controls can change, so the live authorization screen is the source of truth. Start read-only and connect only the account a proven workflow needs.

Approvals and the box computer

Approvals are decision points for consequential work. Read the proposed action and target before continuing. Keep passwords, session cookies, private keys, recovery codes, and unrestricted production credentials out of prompts.

The box is Grok Bot’s working computer environment for files and tools. Isolation helps organize work, but it does not make untrusted code or sensitive data automatically safe. Inspect real files and outputs rather than assuming a chat message proves the task completed correctly.

What Grok Bot is not

  • It is not a guarantee that every task can run without review.
  • It is not an excuse to connect every account “just in case.”
  • It is not officially documented for every operating system or mobile device.
  • It is not usebot.net; this site is an independent editorial guide with no affiliation or endorsement.

A sensible first path

  1. Confirm your device in the platform checker.
  2. Confirm access in the plan finder.
  3. Complete one small, reversible, verifiable task.
  4. Save the method as a skill only after it works.
  5. Add one minimum-access plugin only if manual input is no longer practical.
  6. Create a routine after a successful test run and add a human review gate.

Continue with Getting started or compare the building blocks in Skills, routines, and plugins.

Sources and verification

Last verified: August 27, 2026.

Next: all guides · tools · FAQ