2026-08-27 · Tutorial
How to Pause a Grok Bot From Your iPhone
Boarding group C is calling while a follow-up compose sits unsent on a cloud computer you cannot see. The only useful verb on that iPhone is pause. Resume, run history, and delete exist too. Editing the charter and firing a test do not. This page is the click path: when to freeze, how to freeze, what freeze does not do, and why you still wait for a Mac, Windows, or Linux desk.
It is not the limit catalog. Grok Bot iPhone limits lists every verb the phone refuses. It is not the product tour. Grok Bot on iPhone says what the pocket client is for. Stay here when a job is going wrong in a TSA line and you need the taps, in order, before the send leaves.
Documented scope, from the mobile page: iPhone on iOS 18 or later. On that phone you can pause and resume a routine. Editing and testing a routine still need the desktop app; the phone can now show run history and delete a routine. Teach by demonstration is unavailable on iPhone (skills, routines and automations). Design the airport hour around those sentences. Do not invent a pocket editor or a logout button on top of them.
Confirm iOS 18 and an eligible plan before you hunt the pause control
Pause lives in the Grok Bot iPhone app. The app lives on iPhone running iOS 18 or later (FAQ). Older iOS is not a limited pause mode. It is outside the client list. Check Settings -> General -> About before you spend the minute in a security line assuming the home-screen icon is enough.
iOS 18 is the floor, not a feature pack. Crossing it does not unlock charter edit. It unlocks pause, resume, and run history. If the device in your pocket is not an iPhone on that floor, this click path is not that device. There are Linux desktop and Android apps as of September 2026, and the iOS app also runs on iPad (iPadOS 18 or later). The bot computer is a managed Linux virtual machine. That is not a laptop you can SSH into from the jetway. The platforms list is the matrix.
You still need an eligible plan or the one-time trial. The phone app does not bypass that door. Every paid Cursor plan includes Grok Bot, from Cursor Pro at $20; Cursor Hobby, the free plan, does not, and an individual SuperGrok, SuperGrok Plus, SuperGrok Heavy or X Premium+ subscription can be linked instead. If pause is missing because the account never had Bot, that is the Cursor account explainer, not a hidden setting. Screenshot About once at a desk so you are not debugging an OS floor in a boarding group.
Open Grok Bot on the iPhone and land on the routine that is about to fire
Unlock the phone. Open Grok Bot, not grok.com chat, not Cursor, not Mail. You want the bot that owns the routine, then the routine itself. A routine assigns a workflow to one Bot. Max 50 routines per Bot. Nothing is team-level (skills, routines and automations). Pausing the wrong card leaves the send-capable clock alive.
Exact control labels can move. The documented verbs do not: pause, resume. If you cannot find pause, you still cannot rewrite the charter from this client. Hunt once at a desk on a throwaway routine so the airport hunt is muscle memory, not discovery.
All bots on the account share one persistent cloud computer assigned to the user, not to a bot (computer and apps). Screens are not security boundaries. Cookies, sessions, files, and CLI credentials are shared. Pausing one routine does not pause the machine. Sibling routines keep their clocks. If you cannot tell which routine is about to send, pause every routine you can reach on the send-capable bot, then wait for a desk to sort the names.
Inbox Triage is the shape a follow-up should have been: drafts wait. Lead Scout never contacts anyone. The airport hour fails because a send verb is live on a named routine you can still freeze.
Tap pause, then stay on that screen until the job shows as frozen
This is the whole pocket move. Tap pause on the named routine. Stay until the control shows the job is frozen. A tap you did not confirm is a tap you cannot prove. Individual accounts and self-serve Teams still have no audit view of Bot actions; Enterprise has audit logs and Action Recording (teams and enterprises). The phone will not write you a receipt.
Closing the app does not pause the cloud computer. Locking the phone does not. Airplane mode does not. Radios off stops your view. The managed Linux VM keeps the clock. People switch to airplane mode at the gate, feel safe, and land to a sent folder that filled over Kansas.
Resume is on the same screen. Do not tap it because the buzzing stopped. Resume restarts the same standing instruction.
| Step | What you do | What changes | What does not change |
|---|---|---|---|
| Settings -> General -> About | Confirm iOS 18 or later | Nothing in Grok Bot | Pause still needs the app |
| Open Grok Bot | Land in the pocket client | Nothing yet | The cloud computer still runs |
| Open the named bot | Reach that bot's routines | Your view | Sibling bots, shared cookies |
| Pause the named routine | Future fires stop, if the control took | That routine's clock | Charter, history, cookies, other routines |
| Stay until frozen | Confirm the control | Confidence, not a log | Still no audit view outside Enterprise |
| Lock the phone, or airplane mode | You leave the radio | Your radios | The VM. Pause must already have held |
Write bot name, routine name, and clock time in Notes. iPhone will not keep a pause log.
Treat pause as a freeze of future work, never as a recall of mail that already left
Pause stops the next run of that routine. It does not pull mail out of a customer inbox. It does not unsay a Slack post. It does not move a price in a standing instruction. An approval controls the proposed action and does not reverse work already completed (approvals, security and privacy). Pause is the same shape: interrupt, not undo.
If the send already left, pause is still the right first tap. It stops the retry. It does not repair the first send. Tell the recipient from your own hands. Then wait for a desk. Who is on call is who you page when that first send needs a human, not a second bot.
If the compose is still unsent, pause is the whole win. That is the airport case this page is for. The almost-send sits on the shared computer until a desk can open the screen and park send behind an ask. The phone cannot do that last step.
Do not grade the freeze from chat. The work lives on the cloud computer. If the chat went silent with files half written, that is Grok Bot stalled mid-job, and pause is still the pocket first move so the job does not keep retrying while you travel.
Keep every cookie and session signed in, because pause never logs the computer out
This is the myth that turns a good freeze into a false cleanup. People pause, then tell themselves Gmail is signed out. It is not. Pause does not sign out cookies. Sessions stay. Files stay. CLI credentials stay. Deleting a bot does not remove shared-computer files or sessions either, whether you delete from the phone or a desk (approvals, security and privacy).
The computer is assigned to your user account, not to an individual Bot. Separate bots are not a security boundary. Shared-computer security is that architecture. Pause is a clock interrupt on one routine. It is not a session kill.
The almost-send used a mailbox cookie that is still live. A sibling routine can still open Gmail. If the follow-up card is paused and Mail Cleanup Assistant is still on a weekday clock with the same inbox, you paused the wrong half of the risk. Pause every send-capable routine you can reach. Logout is desk work, in the browser on the Agent Computer. Hosted MCP sign-in tokens stay with Cursor's backend and also do not flip when you pause.
| Thing people think pause does | What actually happens | Where the real verb lives |
|---|---|---|
| Signs Gmail, Slack, or a CRM out | Sessions stay on the shared computer | Desk, in the browser on the Agent Computer |
| Deletes the routine | The routine stays. The 50-cap still counts it | A separate delete, after you inventory sessions |
| Pauses every bot on the account | Only that routine's clock stops | Pause each send-capable routine you can reach |
| Unsends mail that already left | The mail stays sent | Your own hands, then a desk rewrite |
| Rewrites the charter | Standing text is unchanged | Desktop edit |
| Stops a sibling routine | Sibling clocks keep firing | Pause those too |
Leave the routine on the bot card, because pause is not delete
Treat delete as a desk verb, even though the phone now has it: on iPhone you can delete a routine or a bot (mobile). Deleting a Bot also deletes its routines. It does not wipe cookies or files. People who "clean up" from a phone with that control cut the evidence, while a sibling send-capable clock may still be live.
Leave the name. A paused routine you can still see is a routine you can still resume after a desk patch. A deleted bot is a hole in the roster plus leftover sessions. The app keeps the 20 most recent run records per routine. You can read them from iPhone, but only while the routine exists. Wipe the card and you wipe the rows the evening desk needs.
Standup Scribe can sit paused through a flight without hurting anyone, because it DMs you. A send-capable follow-up cannot sit live through a flight. Pause is per routine, not per account. Do not freeze the whole roster because one card scared you, unless you cannot tell which card is the send.
Replay Wrenfield's Terminal C almost-send from the 14:10 call to a frozen compose
Here is the Friday this page is for. Maya runs a weekday follow-up bot for Wrenfield Supply. She meant it to draft. The charter still says send. The 14:00 clock opened Gmail and wrote "Friday 11:00 is locked in, we will send the SOW tonight" to a prospect who has not locked anything. Maya is in SFO Terminal C, boarding group C, 14:35 to Denver. She cannot see the Agent Computer. She can see a Slack ping from a watchdog she built herself, because Grok Bot will not page her.
14:10. Sent is still empty. This is an almost-send. She opens Grok Bot, opens the Wrenfield follow-up card, taps pause, stays until frozen, and writes "Wrenfield follow-up, weekday 14:00, paused 14:11 Pacific" in Notes. She does not resume. She does not hunt an editor.
| Clock | What is true on the cloud computer | What Maya can do from Terminal C |
|---|---|---|
| 14:00 | Routine fires. Gmail compose opens | Nothing. She is in the TSA line |
| 14:10 | Compose still unsent. Watchdog pings | Open Grok Bot. Pause. Confirm frozen |
| 14:11 to 14:34 | Frozen, if pause held | Do not resume. Airplane mode is not a substitute |
| 14:35, wheels up | Still frozen. Run history readable on the phone | Notes only. No charter patch from the app |
| Evening, at a desktop | Still frozen, now fixable | Read history. Edit to drafts only. Test. Then resume |
The phone's whole job is that the send does not leave. That is the difference from the limit-catalog story where the wrong-price mail already sat in a customer inbox. Here you still have a freeze that matters.
If Maya had closed the app instead of pausing, the clock could have hit send over Nevada. If she had resumed at 14:20 because the ping stopped, the same compose could have left. If she had paused Standup Scribe and left the follow-up live, the almost-send would have become a send. Named routine, pause, confirm, Notes, no resume.
Sort the next thirty seconds into pause now, already too late, or wait for a desk
You do not have a diagnosis window in a boarding group. You have a sort. Pause now, already too late for the last action, or wait for a desk.
| Signal | Pause now | Already too late | Wait for a desk |
|---|---|---|---|
| Compose open, Sent still empty | Yes. This page's whole case | No | After pause: read the draft, patch the charter |
| Customer already has the mail | Yes, to stop the retry | The last send. Tell them by hand | Rewrite, test, then resume |
| Chat says working, you cannot see files | Yes, so it stops retrying | Unknown until a screen exists | Stalled mid-job at a desk |
| You want to change a price or a name in the charter | Yes, so the old text stops firing | You cannot edit from iPhone | Desktop edit, then a draft-only test |
| Approval prompt might be waiting | Yes, then Deny it in the app | The phone shows approval requests if you open the app | Approvals walkthrough at a desk |
| You froze the wrong sibling routine | Pause the one you meant | The wrong freeze is still a freeze | Desk to tell the cards apart. Do not resume the scary one |
If you are still hunting an editor at second twenty, you are already in the limit catalog. Switch to pause. If pause is not on the screen, you are on the wrong client, the wrong OS, or the wrong account.
What a Grok Bot is is the object model. This sort is the device that can only interrupt that object.
Park resume in your pocket until a desktop has read the charter
Resume is documented on iPhone. That does not make it a pocket patch. Resume restarts whatever you froze. If you froze a healthy job by accident, and you can see that in a channel outside Grok Bot, resume from the phone is honest. A customer-facing almost-send is not that case.
Hold resume until a supported desktop has opened history, changed the standing text, and tested once. If the evening desk window slips, the routine stays paused through the next morning. A missed follow-up draft is cheaper than a second SOW promise.
The only resume that belongs in a boarding group is the one you can defend in one sentence: you paused the wrong card, the send-capable card is still paused, and this card only DMs you. If you cannot finish that sentence, leave both paused. Silence after pause is not a fix. The charter that wrote "Friday 11:00 is locked in" is still the charter.
Author a pocket-pause line into the standing text so the phone only has to freeze
The airport hour is won or lost at a desk, days earlier. Write the phone rule into the charter while you can still type. The phone will not take new text. Put the line next to the send rule, in the same file. Name the routine, the on-call human, and the desk. Say pause does not log sessions out and does not delete the card.
Bot: Wrenfield follow-up (weekday 14:00 Pacific)
Device split: phone app (iPhone or Android) can pause, approve, read run history, and delete. No editing.
On iPhone: pause the weekday routine if a send looks wrong.
Do not resume from iPhone. Do not hunt an editor. Do not delete.
Pause does not sign out Gmail. Pause does not remove this routine.
Resume only from a desktop after history is read
and this charter says drafts only.
On-call: Maya until 18:00 Pacific, then Jordan with the office Mac.
Boundary: never click Send. Drafts wait in Gmail Drafts.
If Sent is not empty, pause, tell the recipient by hand, wait for the desk.
Paste that at a desk. Prove pause once on a throwaway routine before the first trip. Chief of Staff Briefing can carry the same pocket line even when it never sends. Teach by demonstration is unavailable on iPhone. Do not plan to record a browser workflow in the lounge.
Point the pause ping at a named human, because Grok Bot will not page anyone
Grok Bot does not page, escalate, or keep an on-call calendar. Maya's 14:10 Slack ping existed because she built a watchdog. Pause still works when you happen to open the app. It does not work when you never hear that the compose opened.
Name the human in the charter. Who is on call when a Grok Bot misfires is staffing. This page is the verb that person uses from a phone: pause, then stop. Page the person who can sit at a Mac or a Windows desk after landing. A Linux-only engineer with an iPhone can freeze from the phone and diagnose on the Linux desktop app. An Android-only contractor has the same companion app on Google Play.
If you are the named human and you are in Terminal C, you are pause-only until Denver. If send was parked on ask, the prompt can reach the app on your phone. Deny it there, then pause so the routine stops offering the same send. Write the page path before the trip. Three names can be one person. They cannot be a Slack channel.
Grant that pocket pause looks like full remote control, then name the verbs it still lacks
The strongest case against this page is: pause and resume are on the phone, so the phone is the product, and a desk is nostalgia. It wins in one narrow band. If every routine you leave running is draft-only, DM-only, or a research sheet, and you already trust the charter, a freeze from a seat-back tray is enough. You never need to rewrite in the air. You need to interrupt.
It loses the moment a send, a refund, a calendar cancel, a shared-channel post, or a mailbox delete is live. Those need a rewrite you cannot type and a one-shot test you cannot fire, and they deserve a delete you should not use from a seat that cannot show leftover sessions. Those verbs are the desk.
It also loses the cookie myth. Remote control that cannot log a session out is remote control of one clock, not of the machine. The machine still has Gmail. Sibling clocks still have Gmail.
If pause is enough, the bot is commute-safe. If pause is not enough, the bot does not run across a flight. That is the same boundary as the safety checklist, arrived at from a click path rather than from a consent screen. As of the docs rechecked 2026-09-23, the pocket routine controls are pause, resume, run history, and delete. Build the trip around pause.
Prove pause held by watching the next scheduled clock, not by trusting the tap
A tap is not a test. The test is whether the next fire did not happen. After the next scheduled time, the phone's run history should show no new run. Sent, the watchdog, and a desk later are the other proofs.
If you need proof before you fly, pause a throwaway routine at a desk the day before, watch it skip the next clock, then resume it from the desk. Do not rehearse on the send-capable card at 14:09 in Terminal C.
If pause did not hold, open Grok Bot again. Confirm you paused the named routine. Pause every send-capable sibling you can reach. Do not resume. Do not delete. Closing the laptop at home does not pause the VM. Someone has to tap pause, on a supported client, on the right card. There is no published stall timeout. Do not wait for an automatic kill you have not been promised.
Carry Notes of what you froze, because iPhone will not keep a pause log
The taxi in Denver is when Maya will try to finish the job in Grok Bot iPhone and bounce off the same walls. Write the desk list in Notes while the compose line is still in her head.
| Item to write in Notes | Why the phone cannot close it | What the evening desk will do |
|---|---|---|
| Bot name, routine name, paused-at clock | Pause is not a log | Match the time to the twenty run records |
| Compose line she saw in the ping | A ping is not a record | Confirm against Gmail Drafts or Sent |
| Sent empty, or not | Guessing later is how a second mail leaves | Treat that fact as the incident grade |
| Do not resume from iPhone | Resume is one tap away | Resume only after a draft-only test passes |
| Cookies still live, routine still on the card | Pause is not logout and not delete | Sign out in the browser if the incident needs it |
If dinner eats the desk window, the routine stays paused. Do not resume from the phone because the buzzing stopped. Scheduling is how you keep the next run from firing during dinner. Change the cadence at a desk. If you want a bot that can survive a pause without a customer-facing almost-send, start from Inbox Triage or Lead Scout.
Keep reading: Grok Bot iPhone limits, Who is on call when a Grok Bot misfires, Grok Bot stalled mid-job.
Frequently Asked Questions
How do I pause a grok bot from iPhone?
Open the Grok Bot app on an iPhone running iOS 18 or later, open the bot that owns the routine, and use the pause control on that named routine. Stay on the screen until the job shows as frozen. Closing the app, locking the phone, or turning on airplane mode does not pause the cloud computer. Editing and testing a routine still need the desktop app. If you cannot find pause, you still cannot rewrite the charter from this client. Rehearse the tap once on a throwaway routine at a desk before you need it in a boarding group.
Does pause sign out cookies or delete the routine?
No. Pause stops future work on that one routine. It does not sign out Gmail, Slack, a CRM, or any other session on the shared cloud computer. Cookies, files, and CLI credentials stay. The routine stays on the bot card, and the fifty-routine cap still counts it. Deleting a bot deletes its routines, and that delete now works from the phone too, so do not reach for it by mistake. Sibling routines and other bots on the same account computer keep their clocks unless you pause those too. Logout and teardown are later desk work.
Should I resume from iPhone after I pause at the airport?
Almost never. Resume restarts the same standing instruction you froze. If you paused because a send looked wrong, a pocket resume replays the wrong send. Hold resume until a desktop has opened history, patched the charter, and tested a draft-only one-shot. The only honest pocket resume is an accidental freeze of a job you already trust, confirmed from a channel outside Grok Bot. A customer-facing almost-send is not that case. Silence after pause is not a fix.
What if I paused the wrong routine, or paused too late?
Pause the routine you meant as soon as you can still reach it. If the send already left, pause still stops the next one, and it does not unsend the first. Tell the recipient from your own hands. If you froze a healthy sibling by mistake, leave the scary card frozen until a desk can tell the two names apart. iPhone shows run history but cannot fix either card, and individual accounts have no audit view of bot actions. Guessing from the phone is how a second send leaves. Do not delete from the phone just because you can.