Grok Bot can read your email and post in Slack: here's how it works

Grok Bot is an AI agent from xAI that runs on a cloud computer. It can use programs, browse the web, write and run code, and carry out workflows on its own. It launched in beta in August 2026 and is distributed through Cursor, which according to i-SCOOP is now owned by xAI.

Grok Bot came to Android on September 2, 2026. Previously it was available on desktop and iOS. It is still in beta.

What can it get into?

The bot can connect to services such as Gmail, Google Calendar, Google Drive, Google Sheets, Notion, Slack and 1Password. These are connections to cloud services, not to apps installed on the phone. It can also be hooked up through MCP servers, plugins and skills.

The connection is set up under "Connect apps" in the sidebar, or on mobile via the avatar. The user signs in to the service themselves in their browser.

With Gmail, the bot can search, read, write drafts, send emails and apply labels. With the calendar, it can read, create and update events and check availability. In Sheets it can read and edit cells, and in Slack it posts as the connected user in the channels the user has access to. With 1Password, the user must approve each individual login request.

According to Cursor, an app connection cannot grant more access than the user's existing permissions, and it cannot change sharing settings. Gmail supports only one mailbox at a time, while most other apps can have multiple accounts connected, for example both personal and work.

Security and the workplace

Security is handled with permission rules written in plain language, a review agent that approves or blocks proposed actions, and allow and block lists. xAI itself writes that the rules are a prompt and not traditional code, so the user has to trust that the model follows them.

In companies, team administrators in Cursor can turn off specific apps. Google Workspace administrators must approve Grok via API controls before connections to Gmail, Drive and Calendar, among others, will work. There are known bugs: Zoom authorization fails with error 4700, and SharePoint returns error AADSTS50011 with Application permissions. Cursor suggests Delegated permissions as a workaround.

On mobile

The mobile app requires signing in with a Cursor account. Users can message their bots on the go and continue conversations across devices. Bots keep working in the cloud while the phone is locked and only ask for approval when necessary. Notifications can tell you when a bot has finished or needs input. Updating, restoring and resetting the computer requires the desktop app.

Pricing and limitations

Access comes with certain Cursor plans and with SuperGrok or X Premium+ accounts. The sources disagree on pricing: xAI mentions "Get started for free," while i-SCOOP writes that there is no free version. According to i-SCOOP, the Grok 4.6 model costs $2 per million input tokens and $6 per million output tokens. You cannot choose the model manually, there is no live voice conversation, and the bot cannot get around sites that block automation or require human verification.

The feature descriptions come largely from the maker and the distributor themselves and have not been independently tested.