Grok Bot on iPhone: Setup, Approvals and Limits

The mobile app currently requires an iPhone on iOS 18 or later, internet access, and an eligible Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. account. Sign in with the same Cursor account used on desktop. Grok Bot is not currently designed for iPad or Android, even though the shared computer itself runs in the cloud.

Download Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. from the App Store, choose Login with Cursor, finish authentication in the browser, and return to the app. New users can complete setup and wait for the shared computer. Existing users go to the Bot list already associated with that Cursor account.

Yes. The iPhone app connects to the same Bots, conversations, routines, connectors, and shared cloud computer as desktop. Work keeps running in the cloud when the app closes, so mobile is a control and review surface rather than a second execution environment.

That shared state includes browser sessions and files. Taking over a sign-in from iPhone changes the same computer every Bot uses. Check the account shown on the page before returning control, especially when personal and company identities are both available in the browser.

Mobile continuity is most useful for work that has a clean attention point. Ask the Bot to return when it has a result, question, or approval request rather than sending frequent progress messages. The sidebar and notification state then tell you which thread needs an actual decision.

A mobile conversation accepts text, dictated messages, a new photo, an image or file from the phone, Bot and group mentions, thread replies, and reactions. Drafts are saved per conversation when you navigate away.

• Send a short redirect while work is running when the scope changes.
• Attach a photo when the visual state is part of the evidence.
• Mention a specific Bot when one role owns the next step.
• Use a thread when feedback belongs to one result or approval card.
• Write a reply for changed instructions; a reaction should not carry a safety-critical decision.

The phone is good for narrowing work, less good for specifying a new multi-system process from scratch. Link the source, name the deliverable, and state the approval boundary in the same message. If the task needs a long skill edit or a detailed routine test, move to desktop rather than compressing the instruction into a hurried mobile note.

Open the computer from a conversation to watch browser or desktop work, inspect the current screen, take over for a password or verification step, and return control to the Bot. The screen is the same shared computer used by the full Bot roster.

1. 1Open the approval request and read the target, operation, and values.
2. 2Use Approve once only when the shown action matches the intended scope.
3. 3Choose Deny when the target or effect is unclear, then ask for a draft or explanation.
4. 4For a password, passkey, two-factor code, or CAPTCHA, open the computer and take control yourself.
5. 5Confirm the account and page state before returning control to the Bot.

Approval does not undo earlier work. If the task changed while you were away, check the recent messages and action state before approving the last card in isolation. A card can be precise about its immediate operation while the surrounding plan is now wrong.

Auto Review settings may appear on mobile during rollout, but personal rules are stored on the current desktop and synced to its Grok Bot computerThe persistent cloud computer shared by all Grok Bots on one user's account, including its files, browser sessions and command-line credentials. Press Enter for the full definition.. Do not assume a mobile screen proves every desktop installation has the same local rule set.

Use the plus control on the home screen for New Agent or New Group Chat. You can edit a Bot profile, manage group members, pin or hide a conversation, and delete a Bot. Remember that deleting a Bot also removes routines it owns but does not clean shared files or browser sessions.

Search can find conversations and available message, file, link, or routine results. Search availability can vary during rollout. When a cross-conversation result is missing, open the known Bot and use its history rather than treating the search result as proof that the work does not exist.

Groups work best when one Bot owns each stage. Mention the owner directly when a handoff matters, and use @everyone sparingly. The shared group transcript makes the transfer visible, but it does not isolate the Bots' computer access from one another.

Open a Bot's profile to inspect its routines. On iPhone you can see a routine's schedule, next run, and instruction, then use Active to pause or resume it. That is enough to stop recurring work when its source changes or a result looks wrong.

If a routine misses its run, check that it is active and that the scheduled time zone is the one you expected. Then move to desktop for run history and Test run. Testing can perform real external actions, which is another reason the product keeps that control out of the quick mobile path.

Allow iOS notifications during first run if a Bot may finish or request approval while you are away. Both the device permission and that Bot's notification setting must allow delivery. Mobile push is still rolling out, so some accounts may rely on in-app attention states even when settings look correct.

Needs attention marks a question, approval, or handoff. Unread activity marks a new result. Opening the conversation marks current activity read, and the conversation menu can mark it read or unread manually. Treat those states as routing signals, then inspect the actual action before deciding.

A missing push does not mean cloud work stopped. Open the app and check attention states, routine status, and usage. If notifications matter operationally, test one safe completion and one approval request on the actual iPhone before depending on them.

Desktop remains the full administration and creation surface. Use it for Teach a task, routine editing and testing, detailed run history, routine deletion, advanced computer recovery, and controls that have not reached iPhone. Mobile is strongest for messaging, review, takeover, and pausing work.

When the shared computer is unreachable, try reopening the conversation and restarting the app. Recovery, Update Agent Computer, and Reset Agent Computer belong on desktop, with reset last because it can lose recent unsynced work. A disconnected phone does not necessarily mean the Bot's cloud work or saved conversations are lost.

For the full computer and recovery model, use Grok Bot computerThe persistent cloud computer shared by all Grok Bots on one user's account, including its files, browser sessions and command-line credentials. Press Enter for the full definition. and apps. For routine authoring rather than mobile supervision, use Grok BotAn early AI teammate product from SpaceXAI and Cursor that works across apps on a persistent cloud computer and asks for approval on selected actions; launch materials describe it as beta, but Cursor says Beta Services terms do not apply. Press Enter for the full definition. skills and routines.