Grok Bot now signs in with Okta FastPass on its own computers

Grok Bot's computers can now pass Okta FastPass. A setup script installs Okta Verify on the Bot's computer, so a Bot can sign in to your Okta-protected apps in its browser. It's Enterprise only.

Slide text

Grok Bot computers can now sign in with Okta FastPass

Okta Verify FastPass Okta-protected apps

Enterprise only · set up by an Okta admin

docs.x.ai/grok-bot/okta-fastpass

Until now, a sign-in rule that required FastPass failed in the Bot's browser. With the setup, it passes. A rule that demands a managed device still fails, because the computer isn't enrolled in device management.

Slide text

Without it, a FastPass rule fails in the Bot's browser

FastPass rule Passes after setup

Okta Verify factor Passes after setup

Managed-device rule Still fails

The computer runs Linux and isn't enrolled in MDM

docs.x.ai/grok-bot/identity-and-access

The script already ships on every Grok Bot computer. An admin turns on Okta Verify for Linux, adds the script in the Cursor dashboard, and each computer enrolls once. Enrollment survives restarts.

Slide text

One Team Setup Script entry installs Okta Verify on every computer

01Turn on Okta Verify for Linux in Okta

02Add the script in the Cursor dashboard

03Enroll each computer once

Okta Verify 7.1.3.0 · a failed setup never blocks the computer

docs.x.ai/grok-bot/okta-fastpass

Pressing Control V in the passcode prompt crashes Okta Verify on Linux, so paste with a right-click. You get about 30 seconds to enter it, and every Bot on the computer shares one window.

Slide text

Paste the Okta Verify passcode with right-click, not Ctrl+V

Ctrl+V Crashes Okta Verify on Linux

Passcode Enter it within about 30 seconds

One window Shared by every Bot on the computer

The window closes after 5 minutes without a sign-in

docs.x.ai/grok-bot/okta-fastpass · Limitations

A new link opens a Bot's chat from a shortcut or another app, with your message in the box. It holds up to 1,000 characters and waits for you to send it.

Slide text

A link can now open a Bot's chat with your message already typed

Link grokbot://app/v1/prompt?id=…&text=…

Text Up to 1,000 characters, waits for you to send

No Bot ID Opens your primary Bot

docs.x.ai/grok-bot/deep-links

Enterprise admins can now force Bot traffic through members' own computers, or turn that off for everyone. With Always on and no computer connected, the Bot refuses those sites.

Slide text

Enterprise admins can now lock how Bot traffic is routed

Always on Routes through each member's computer

Members decide The default

Always off Traffic goes through the cloud

Always on with no computer connected: routed sites are refused

docs.x.ai/grok-bot/teams-and-enterprises · docs.x.ai/grok-bot/settings-and-notifications

Some apps, like Notion, now take a second account. Give each one a label, such as work or personal, and tell the Bot which to use. Every Bot on your account can use both.

Slide text

Apps like Notion can now connect a second account

work personal

“Use my work Notion.”

docs.x.ai/grok-bot/computer-and-apps · Connect a second account

Personal Bots no longer have a description or a settings page. To change what one does, tell it in chat, and it keeps the rule in its memory. A Team Bot still has a description its owner can edit.

Slide text

To change a personal Bot, you now just tell it in chat

Personal Bot No description or Bot settings page

Team Bot Keeps its description under About

docs.x.ai/grok-bot/bots

An hourly routine, or a Slack trigger on a busy channel, can spend a week of usage in a day. Pause what you don't need and widen schedules before you raise your limit.

Slide text

A busy routine can spend a week of usage in a day

Spends more Hourly schedules, busy Slack triggers

Spends usage Every run, including Test

Spends nothing A routine that never runs

docs.x.ai/grok-bot/skills-routines-and-automations

On Android, Grok Bot 1.18 removed the ability to see your phone's notifications. If you granted that access earlier, you can take it back in your phone's settings.

Slide text

Grok Bot for Android no longer reads your phone's notifications

Since Android app 1.18.0

Old permission Remove it in your phone's notification settings

docs.x.ai/grok-bot/mobile

If your Okta policies require FastPass, I'd set up Okta Verify on the Bot computers rather than switch FastPass off company-wide. The steps are in the guide Set up Okta Verify and FastPass.

Slide text

If your Okta policy requires FastPass, set it up rather than loosen the policy

Set up Okta Verify and FastPass

Enterprise only · Team Setup Scripts

docs.x.ai/grok-bot/okta-fastpass · docs.x.ai/grok-bot/identity-and-access