2026-08-27 · Reference
Grok Bot iPhone Limits: What Still Needs the Desktop App
Correction, 6 September 2026. When this page was written the iPhone app could only pause and resume a routine. The mobile docs (updated 2 September 2026) now describe an app for iPhone and Android that messages bots, creates them, approves steps, takes over the computer for a login or code, and pauses routines. What has not changed is the point of this page: editing a routine, reading its run history, testing it and deleting it still need the desktop app. As of 23 September 2026 that list is shorter: the phone now shows run history and deletes a routine, and only editing and testing still need the desktop app.
The wrong-price follow-up already left from the lounge Wi-Fi, and you cannot rewrite the charter from the jetway. That is the grok bot iphone edit limit in one scene. Pause works. Resume works. Run history and delete work. Charter text, routine settings, and a one-shot test do not.
This page is that limit. Grok Bot on iPhone is the other half of the pair: what the app is for, as a pocket remote next to a desk you still have to own. Stay here if you opened the phone to fix a bad send. You will not fix the send. You will freeze the next one, if pause holds, and you will wait for a Mac, Windows, or Linux machine.
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 on top of them.
Call grok bot iphone edit a missing surface, not a delayed menu
People treat missing buttons as a UI delay. They swipe, they hunt Settings, they assume the charter is one more tap behind a chevron. Grok Bot iPhone is not hiding an editor. The documented mobile routine controls are pause, resume, run history, and delete. The documented desk verbs are everything else that looks like authorship.
A charter is standing text the bot reads when you are not in the room. Changing that text is an edit. Changing a trigger, a cadence, or a connected account is an edit. Firing a one-shot to prove a patch is a test. Neither verb is on the phone. Opening the last twenty run records and removing the routine or the bot now are.
The work still runs on the persistent cloud computer assigned to your user account, not to a bot (computer and apps). The phone is a remote for a routine that already exists: it can pause it and approve its steps, but not change it. If the charter is wrong, the phone cannot make it right. What a Grok Bot is is the object model. This page is the device that cannot change that object.
Separate pause from rewrite so freeze never masquerades as a patch
Pause stops future work on that routine. It does not rewrite a sentence. It does not unsay a send. It does not move a price from 3900 to 4900 in a standing instruction. Resume restarts the same standing instruction. If you paused because the instruction is wrong, resume is the same mistake with a later timestamp.
That swap is how airport hours go badly. The send already happened. The instinct is to "fix it in the app" so the next run is clean. The app will not take the fix. If you resume because the buzzing stopped, you restarted the broken job. If you leave it paused, you bought time. Time is the only pocket patch.
An approval is not a rewrite either. It controls the proposed action and does not reverse work already completed (approvals, security and privacy). Denying a later prompt leaves the first mail in the inbox. How to set Grok Bot approvals parks send before you travel. It is not a jetway editor.
Remember one line at the gate: pause is an interrupt, rewrite is desk work, resume is a bet that the frozen job is still the job you want.
Inventory the desk-only verbs before you leave for the airport
Do this once at a desk, on paper or in Notes, before you pack. The feeling at the gate says "I have the app, I can handle a misfire." The inventory says otherwise.
| Verb you will want at the gate | Grok Bot phone app | Desktop app | What the jetway actually offers |
|---|---|---|---|
| Rewrite the charter, trigger, or cadence | No | Edit | Notes. The Grok app will not take the new text. |
| See the last runs, including how many already sent | Run history | History | Read Run history on the Bot profile, then check Sent. |
| Fire a one-shot that drafts only, to prove a patch | No | Test | You cannot prove a patch from iPhone. |
| Remove the routine or the bot | Delete | Delete | Possible. Leave it paused anyway until a desk. |
| Stop the next run | Pause | Pause | Pause. That is the main pocket move. |
| Restart a paused routine | Resume | Resume | Resume only if you already trust the charter. |
| Record a browser workflow as a skill | No | Teach by demonstration | Unavailable on iPhone. Do not try. |
Pause and resume are the documented mobile pair. Editing and testing a routine still need the desktop app; the phone can now show run history and delete a routine (mobile). Teach by demonstration records up to ten minutes of visible browser interaction, captures no microphone audio, produces a draft skill, and is unavailable on iPhone (skills, routines and automations). iOS 18 or later is the floor for the install (FAQ). Crossing it does not unlock grok bot iphone edit.
Replay a bad follow-up from the jetway until the desk is the only remaining tool
Here is the Thursday this page is for. You run a weekday follow-up bot against a pipeline sheet. You meant it to draft. The charter still says send, or send sits on an approval nobody is watching. Either way, the mail can leave.
11:18, lounge, boarding group B. The phone buzzes. A customer received "the 14-seat plan is $3900." The live number is $4900. The bot pulled a stale cell, or a sibling row. You open Grok Bot iPhone to rewrite the price line. You can pause, and Run history shows whether this is the first send or the fifth. You cannot edit the charter or test a draft-only one-shot. You could delete the routine, but the evidence would go with it. You pause.
| Clock | What already left | What you can do from the jetway |
|---|---|---|
| 10:05 | First weekday pass. You were in security. | Nothing. You were not in the app. |
| 11:18 | Customer mail with the wrong price. | Open Grok Bot iPhone. Pause. |
| 11:19 to 13:35 | Frozen, if pause held. No new sends. | Tell the customer the number is wrong. Do not resume. |
| 13:40, landed, no laptop | Still frozen. Run history readable on the phone. | Taxi Notes: what sent, who you told, do not resume. |
| Evening, at a desktop | Still frozen, and now fixable. | Read history. Edit. Test a draft-only one-shot. Then decide on resume. |
11:19 to 13:35 is the phone's whole job: the next send does not leave. The first send stays sent. Pause is not undo. Individual accounts and self-serve Teams still have no audit view of Bot actions; Enterprise has audit logs and Action Recording (teams and enterprises). Your sent folder and the twenty run records, which the phone can show, are the evidence.
If send was parked on ask, the prompt could reach the phone app as an approval request; push delivery is still rolling out, so open the app rather than wait for a buzz. That is the approvals walkthrough, not a phone failure. If a desk preview would have shown a silent sit, restart without doubling the work is the desk protocol. Neither is a pocket rewrite.
Inbox Triage is the shape this follow-up should have been: drafts wait. Lead Scout never contacts anyone. The Thursday fails because a send verb was live in a boarding group.
Hold resume after a misfire until the charter text actually changes
The buzzing stops after you pause. That silence feels like a fix. It is not. The charter that sent $3900 is still the charter. Resume replays it.
Hold resume until a supported desktop has changed the text and you have tested once. If the evening desk window slips, the routine stays paused through the next morning. That is the correct outcome. A missed follow-up draft is cheaper than a second wrong-price send.
The only resume that is safe from the phone is the one where you froze a healthy job by accident and you can see that in a channel outside Grok Bot: your own DM, a draft folder that looks right, a sheet that did not write outbound mail. A customer-facing send is not that case. Do not resume a send-capable routine from the jetway because the cabin door closed and you want the problem to be over.
Resume is documented. It is not a patch installer. It is a restart of whatever you froze.
Reconstruct the damage from the sent folder and the phone's run history
The app keeps 20 most recent run records per routine. Those records live with the product. Grok Bot iPhone shows them as Run history on the Bot profile, and so does the desktop client.
Twenty is a short window if a routine is looping. A misfire that sends every few minutes can rotate the evidence off the list before you sit down. Pause early so 10:05 and 11:18 are still readable at 20:10. Wait until the hotel to pause and you may only see the last twenty copies of the same price.
Beside that list, the mailbox is the log. Open Sent. Count the threads. Write the names and the wrong number in Notes. A bot that only browsed and wrote nothing you can see from another app is a bot you cannot reconstruct from a seat.
A routine assigns a workflow to one bot. Max 50 routines per bot. Nothing is team-level. Deleting a bot deletes its routines. Creating and editing routines is not available from iPhone. Read the twenty-record window on the phone before it rotates.
Postpone every one-shot test until a supported desktop can prove it
The patch you want at the gate is "change the price rule, then run once, then resume the clock." Testing is a desktop verb. The phone cannot fire the one-shot. A theory you type into Notes is untested. Resume would turn that theory into another send.
So the airport sequence is shorter than the one in your head. Pause. Notify the customer if mail already left. Write the suspected cause. Stop. The one-shot happens at a desktop, against a draft-only charter, on a thread you already control. If the one-shot still tries to send, you have not patched enough. Do not resume the live clock.
Grok Bot stalled mid-job is the desk protocol when a preview looks frozen and you are tempted to type "start over." Start over is how a half-finished write becomes two writes. That needs files and a computer preview. iPhone will not give you those. Pause so the job does not keep moving while you travel to a machine that can list the folder.
Defer bot and routine deletion until a workstation can inventory leftover sessions
You can now delete a routine or a bot from Grok Bot iPhone. Leaving it paused until a desk is still the correct instinct.
Deleting a bot deletes its routines. It does not wipe the shared computer. Cookies, sessions, files, and command-line credentials stay. Screens are not security boundaries. The docs say not to use separate bots as a security boundary (approvals, security and privacy). Deleting from a phone still leaves those logins behind. Pause is the pocket move. Teardown is desk work. The shared-computer write-up is that architecture. Do not sign out of the Grok app thinking that signs the bot out of Gmail. Your phone session is not the cloud computer's browser.
Author the never-send follow-up at a desk so the pocket client only has to freeze
If the only remote lever is pause, the charter has to assume a freeze mid-run, and it has to assume you cannot edit it from a jetway. One pass per run. No self-retry. End with a report you can read without opening run history.
Paste this at a Mac, Windows, or Linux machine. Change the sheet name and the price column.
// AIRPORT-SAFE FOLLOW-UP
You draft weekday customer follow-ups into Gmail drafts only.
Never send. Never reply-all. Never CC. Never BCC. Never forward.
// PRICE RULE
Read price only from column LivePrice on the pipeline sheet named
PIPELINE-LIVE. If LivePrice is blank, skip the thread and say so
in the report. Never invent a number. Never reuse a price from
another row.
// ONE PASS
One draft per thread per weekday. If a draft already exists for
that thread today, skip. Do not retry because a draft might not
have saved. Do not schedule a follow-up run from inside this run.
// BOUNDARY
Never send, never post, never delete mail, never spend, never
cancel. If finishing would require any of those, stop. Failing
the task is the correct outcome.
// REPORT I CAN READ WITHOUT HISTORY
End every run with: threads read, drafts created or skipped, the
LivePrice value you used or the skip reason, and anything that
looked like a loop. Assume I am at an airport and cannot edit
this charter or test a fix until I reach a desk.
Inbox Triage never sends, so a freeze cannot unsay mail that never left. Mail Cleanup Assistant deletes, which is not flight-safe. Standup Scribe is only travel-safe if it posts to your own DM. You cannot paste that charter from iPhone into Grok Bot. Author it before you travel. The pocket client then only has to freeze.
Check the phone for the send approval before you assume it waited on a Mac
Send on ask is not only a desk prompt. The phone app shows approval requests with Allow and Deny. Push delivery is still rolling out, so if you parked send and then left the house, open the app and look rather than wait for a buzz.
If the bot could send without asking, the mail left. If it could not, a prompt may be sitting in the app. Deny it from the gate. Grok bot iphone edit will not rewrite the charter behind that prompt.
How to set Grok Bot approvals parks send, pay, delete, and publish, and lets drafts finish on a desktop. Draw the approval line on reversibility is why send is not a bulk rename. Neither article installs an editor on iOS. If you do not know whether a prompt is waiting, pause. Diagnose at a desk. If the screen looks like a silent sit, use the stall restart, not a second copy of the original job.
Classify each bot by whether a late pause still leaves a customer-facing send
The iPhone limit does not change what a bot is allowed to do. It changes what you can do about a bot that is already doing it. Sort the roster by that gap before you fly.
| Job you want to leave running | Late pause enough on a flight? | Why |
|---|---|---|
| Inbox Triage drafting replies | Yes, if it never sends | Pause does not unsend. Draft-only makes that irrelevant. |
| Lead Scout writing a research sheet | Usually | Spreadsheet rows you can ignore. No outbound mail. |
| Chief of Staff Briefing into a private doc | Usually | A freeze leaves a partial brief, not a customer message. |
| Churn Watch producing an internal list | Usually | A list is not an action. Pause is plenty. |
| Standup Scribe to your own DM | Yes, if it cannot hit a shared channel | A duplicate DM is recoverable. Pause stops the next one. |
| Mail Cleanup Assistant deleting mail | No | Delete is not undo. A late pause leaves mail gone. |
| Any bot that sends, posts, spends, or cancels | No | Pause is not reverse. Do not schedule these across a flight. |
The test is whether a freeze forty minutes late leaves an acceptable world. Draft-only bots pass. Customer mail, ledgers, and shared channels fail. Undo is not a product claim. Edit is not on the phone. Least privilege is the same rule from the other side: if the irreversible step already happened, the phone can only pause the next one.
Grant that Notes plus pause feels like editing, then name the verbs it still lacks
The strongest objection is "I will rewrite the charter in Notes, pause until I sit down, and that is the same as editing." You captured the patch. The bot is frozen. Tonight you will paste. Why is a missing editor a limit rather than a delay?
Grant the case its hour. For a fleet that is already draft-only, Notes plus pause is a workable handoff. The flight does not need a workstation if the worst case is a duplicate draft. Two verbs still sit outside that story, and a third gap follows from them. They are why grok bot iphone edit is not a real move.
You cannot apply the Notes text. The standing instruction is unchanged until a desktop client takes the edit. If the evening slips, tomorrow's clock either stays paused or you resume the broken charter.
Run history on the phone narrows the cause, but a theory you cannot test may still be wrong. The stale price may be a sheet problem, a sibling row, or a retry. Guessing is how people paste the wrong patch at 20:10.
You cannot test. A pasted charter that still contains send will send on the next clock. Notes plus pause is a delay. It is not an edit, not a diagnosis, and not a proof. A person whose only supported device is the iPhone does not have a slower editor. They have pause and resume for routines they have no way to change.
Hand the taxi ride a patch list the Grok app cannot execute
The taxi is when you will try to finish the job in Grok Bot iPhone and bounce off the same walls. Write the desk list in Notes while the wrong price is still in your head. The phone will not apply it.
| Item to write in Notes | Why the phone cannot close it | What the desk will do |
|---|---|---|
| What you paused, and at what clock time | Pause is not a log | Match the time to run history |
| Who already received the bad number | Pause does not tell you who got mail | Confirm against Sent and against the twenty records |
| The suspected cause (stale cell, sibling row, retry) | Unverified until a desk test | Keep or discard the theory after you read runs and test |
| The charter line you will change | Cannot edit from iPhone | Paste the change. Then test once. |
| Do not resume until that test passes | Resume from the phone would skip the test | Resume only after the one-shot stays on drafts |
| Who you already told | Not a Grok Bot action | No bot step. You already did this. |
Skip that list and 20:10 becomes a hunt through Gmail while the paused bot sits there. 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.
Ban send-capable clocks from any window that overlaps a flight
If you cannot rewrite the charter from a jetway, do not let a send-capable clock fire while you are on a jetway. Sends, shared-channel posts, mail deletes, refunds, calendar cancels, anything that spends: those wait for a desk, or for a bot that is not scheduled across the flight. Drafts, private docs, research sheets, and DMs to yourself can run, because a late pause leaves extra drafts rather than a public number.
That is the same boundary as the safety checklist, arrived at from a missing editor rather than from a consent screen. Grok Bot iPhone does not make a dangerous bot safer. It makes a safe bot interruptible.
The phone app does not bypass eligibility, and it does not add an editor when the door is open. Confirm platforms on the supported list: macOS, Windows and Linux desktops; iPhone (iOS 18 or later) and Android (9 or later) phones. iPad runs the iOS app. Prove the missing verbs once at a desk: try to edit and test from the phone. Confirm you cannot. Then prove pause, run history, and delete on a throwaway routine. If you want grok bot iphone edit, that product is not this product, as of the docs rechecked 2026-09-23.
Keep reading: Grok Bot on iPhone, How to set Grok Bot approvals, Grok Bot stalled mid-job.
Frequently Asked Questions
Can I edit a Grok Bot charter from iPhone?
No. Grok bot iphone edit is not a documented surface. On iPhone running iOS 18 or later you can pause and resume a routine, view its run history, and delete a routine or a bot. You cannot edit a charter, a trigger, or a cadence, or test a routine; those need the desktop app. Teach by demonstration is also unavailable on iPhone. The bot still runs on the account cloud computer while you travel. For routines, the phone interrupts, restarts, reads, or deletes one that already exists.
A bot sent a bad email while I was at the airport. What can I do on the phone?
Pause the routine and read its run history, then stop. Do not resume, and do not hunt for an editor that is not there. Pause does not unsend mail that already left, so tell the customer the correction from your own hands. Write down what you saw in Sent, including the wrong number and the time. Fix the charter at a desktop, test a draft-only one-shot, and only then decide whether to resume. If send was supposed to wait on an approval, look for that prompt in the phone app and deny it.
Does pausing a routine unsend mail that already went out?
No. Pause stops future work on that routine. An approval controls a proposed action and does not reverse work already completed, and pause is the same shape: it is not undo. Mail that already left stays in the customer's inbox. There is no audit view of bot actions outside Enterprise, so reconstruct what left from Sent and from the twenty most recent run records, which the phone can show. Use the phone to freeze the next send, not to rewind the last one.
What machine do I need before I can rewrite or test a routine?
A Mac, a Windows PC, or a Linux machine running a supported desktop client. Platforms are macOS on Apple silicon and Intel, Windows on x64 and Arm64, Linux on x64 and Arm64, and iPhone (iOS 18 or later) and Android (9 or later) companion apps that can pause routines, read their run history, delete them, and approve steps, but not edit them. The Linux desktop app arrived in 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 open at the gate. If the iPhone is the only supported device you have, you can freeze, restart, read, and delete existing routines, and you cannot author or test them.