2026-08-28 · Guide

PTO Coverage for a Live Grok Bot

Friday still has ninety minutes on the clock, the intern wants the Cursor password, and the live grok bot that drafts customer follow-ups is set to fire at 07:00 every weekday you will be gone. That password is not coverage. It is the whole computer walking out of the building for eight days.

PTO coverage for a live grok bot is three moves: pause every send-capable routine on the last desk day, name a cover person with their own eligible account, and recreate only the jobs that must still fire on that person's computer. Routines are not team-level. The cover cannot inherit yours. From the phone app (iPhone or Android) you can approve steps, pause or resume a routine, open its run history, and delete it, but not edit it. Editing and testing wait for a desktop app.

This page is a planned absence. It is not a 3am page (who is on call), not the tap path for a freeze in a security line (how to pause from iPhone), and not the intern who asked for the research bot by name (share a grok bot). Stay here when the calendar already shows empty workdays and a live bot is still on a weekday clock.

Write PTO coverage as pause plus a named desk, never as a borrowed Cursor login

Write the plan as names and verbs. Coverage is a person at a supported desk, on their own eligible seat, with a written list of which clocks stay paused and which jobs get recreated. A Slack channel named #cover is not a desk. "The intern will keep an eye on it" is not a roster.

All bots on an account share one persistent cloud computer assigned to the user, not to a bot (computer and apps). Screens are not security boundaries. Do not use separate Bots as a security boundary (approvals, security and privacy). Cookies, sessions, files, and command-line credentials are shared. Handing the intern your login hands them Gmail, staging, CLI tokens, and the home directory. Deleting a bot later does not take those with it.

Name the cover before the last Friday. Supported clients are macOS (Apple silicon and Intel), Windows (x64 and Arm64), and iPhone on iOS 18 or later (FAQ). There are Linux desktop and Android apps as of September 2026, and the iOS app also runs on iPad (iPadOS 18 or later). The agent computer is a managed Linux VM, not a laptop the intern can SSH into. A Linux-only cover can pause from a phone and recreate a routine on the Linux desktop app. Write three verbs into every send-capable charter: pause before leave, recreate on the cover's seat if the job must run, never share the password. Inbox Triage is the shape a follow-up desk should already have: drafts wait.

Pause every send-capable clock on the last Friday you still have a Mac

A live routine does not care that your calendar is empty. Closing the laptop does not pause the cloud computer. Airplane mode does not. A Slack OOO does not. The managed Linux VM keeps the clock (skills, routines and automations).

Do this at a desk on the last day you still have a Mac, Windows, or Linux machine. Open each send-capable bot. Pause every routine. Stay until frozen. Individual accounts and self-serve Teams still have no audit view of Bot actions; Enterprise has audit logs and Action Recording (teams and enterprises). Pause freezes future work. It does not recall mail that already left. An approval controls the proposed action. It does not reverse work already completed.

Pause does not pause the machine. If Mail Cleanup Assistant still has a weekday fire on the same Gmail cookie as Follow-up Clerk, you paused the wrong half of the risk. Pause every send-capable routine you can reach. Write the names in a note you own. Do not resume from the airport. Resume restarts the same standing instruction.

Recreate only the jobs that must fire on the cover's own eligible computer

Most live bots should stay paused for a founder leave. The intern does not need your customer follow-up clerk or your mailbox cookie. They might need a Monday standup for their own mouth, or a morning brief of their own calendar. Those are new jobs on a new computer. They are not a transfer.

A routine assigns a workflow to one Bot. Max 50 routines per Bot. The app keeps the 20 most recent run records per routine. Deleting a Bot deletes its routines. Nothing is team-level (skills, routines and automations). There is no documented move of a named bot, a computer, or a routine onto another person. Each eligible user gets their own persistent cloud computer.

If the cover must run a job, they create it on their account, on a bot they own, from a Mac, Windows, or Linux desktop client. iPhone cannot create, edit, or test a routine. Teach by demonstration is unavailable on iPhone and is not a PTO clone button. Paste the charter as text. Export the /workspace pack they actually need. Point them at Chief of Staff Briefing or Standup Scribe so they recreate the job shape, not your sessions.

Do not recreate send-capable follow-up on the intern's seat "just in case." If you are the person who would have sent, the honest coverage is pause. Churn Watch is a read-and-flag shape. If that flag must still land in a human folder, recreate it on the cover's computer with the cover named as owner, and keep send off. How to schedule a routine is the create-and-verify how-to.

Count the cover's existing routines from a desk before they paste. A fifty-first routine does not schedule. The cap is per bot, not a team pool. The 20 run records are not an audit log (Grok Bot has no audit view outside Enterprise). Leave your live bot paused, not deleted (Grok Bot routine did not run).

Refuse eight days of intern coverage that starts with the founder password

The intern is in the office. You are on a plane. The bot already knows your sources. A password DM looks like eight days of continuity. It is eight days of the intern sitting inside your user account.

They get the persistent cloud computer assigned to you: every bot screen, cookies, sessions, files, and CLI credentials. Hosted MCP sign-in tokens stay with Cursor's backend (teams and enterprises), and they still act as you because they are signed in as you. Individual accounts and self-serve Teams still have no audit view of Bot actions; Enterprise has audit logs and Action Recording. Changing the password on day nine does not rewind copies from day two. What Grok Bot actually isolates is the architecture. The Hobby exclusion page is why Cursor Hobby, the free plan, is not a door. Neither page is permission to lend them yours.

Walk Maren's 21 August leave from 16:40 desk to Ned's 16:52 password DM

Maren is the founder of Nockfield, a nine-person product shop. Ned is the intern through September. This story is invented. The eight-day clocks are an arbitrary example. The architecture is not.

Friday 21 August 2026, 16:40. Maren still has Follow-up Clerk on Cursor Pro at $20 a month, the cheapest paid path that includes Grok Bot, checked 23 September 2026 (Cursor pricing). The bot owns four weekday routines, including a 07:00 fire that can send. Morning Brief sits on a second card in the shape of Chief of Staff Briefing: read only. Standup Pack sits on a third. All three share one computer and one Gmail cookie.

At 16:52 she DMs Ned the Cursor password and a screenshot of Follow-up Clerk. She does not pause. Ned is on Cursor Hobby. Hobby does not include Grok Bot. Saturday 22 August, 07:18, he taps resume from iPhone on a compose sitting on ask. A follow-up leaves to a renewal thread she had been handling herself. Monday 24 August, 09:04, he deletes Follow-up Clerk because three cards look like duplicates. The four routines die. The Gmail session stays. Sunday 30 August she returns to a missing card, a customer who already has the mail, and a zip of /workspace on his laptop. Changing the password does not rewind Saturday.

The rewrite, same Friday, 16:10: she pauses Follow-up Clerk and the send-capable sibling on Mail Cleanup. She copies two charters into a doc. Ops buys Ned a self-serve Cursor Teams seat for the month, confirmed on Cursor team pricing the morning they pay. He recreates a read-only brief on his own computer, send off. Follow-up Clerk stays paused until 30 August. No password leaves Slack.

Walk that table once before you pack. The missing Friday pause is the failure, not the intern.

Leave the founder's cookies signed in because a paused computer is still logged in

People pause, then tell themselves Gmail is signed out for the week. 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 (approvals, security and privacy). Pause is a clock interrupt on named routines. It is not a session kill. If you paused and also handed Ned the password, you froze the clock and then gave him the house key.

Logout is desk work in the browser on the Agent Computer, only for sessions you will re-auth when you return. Do not revoke the mailbox as a 16:55 panic unless send is already paused. Hosted MCP tokens do not flip when you pause. Privacy Mode (Legacy) blocks Grok Bot entirely: do not use it as a PTO switch unless you intend to stop every bot on the account. An intern on your session is still you, including on the VM's static egress IPs. How to set approvals parks send on ask. Ask is not a babysitter. Pause send-capable clocks anyway.

Limit the airport iPhone to pause and resume, then wait for the cover's desk

Documented mobile scope, from the mobile page: iPhone on iOS 18 or later 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. You will not rewrite Follow-up Clerk, fire a test, or create Ned's replacement routine from the jetway.

If Friday's desk pause did not happen, the airport tap is salvage. Open Grok Bot, not grok.com chat, not Cursor, not Mail. Pause each send-capable routine you can reach. Stay until frozen. Write the names and clock time in Notes. Do not resume when boarding group C is called. Ned cannot create the replacement brief from a pocket either. If the only machine in his bag is an iPad, it runs the iOS app (iPadOS 18 or later) with the phone's limits, so it cannot create the routine either; a Linux laptop runs the desktop app as of September 2026 and can (supported platforms). Staff the last Friday as a desk hour for both people.

Grok Bot iPhone limits is the verb catalog. This page is why those limits make the last desk day load-bearing for a planned leave. A 3am misfire while you are already gone is who is on call. For PTO, the on-call human for send is nobody, because send is paused.

Pay for the cover's Teams seat instead of lending your Cursor login

Ned on Hobby cannot open Grok Bot. Cursor Hobby, the free plan, does not include it; every paid Cursor plan does, from Cursor Pro at $20. An individual SuperGrok subscription can be linked instead. Eligible paths, checked 23 September 2026: Cursor Pro, Pro+ and Ultra, Cursor Teams, a linked individual SuperGrok, SuperGrok Plus, SuperGrok Heavy or X Premium+ subscription, plus a one-time trial (FAQ, Cursor pricing). Confirm the live invoice the morning you pay.

Every seat on a self-serve Cursor Teams plan includes Grok Bot as a per-person stamp (Grok Bot on Cursor Teams Standard). Cursor Pro at $20 is the cheapest paid individual path. Pro+ at $60 and Ultra at $200 include it with more weekly usage. A Teams Premium seat is the same Bot product on a richer Cursor SKU. None of those SKUs mint a shared bot. Each seat gets its own cloud computer.

Buy the seat (or a qualifying trial) on Friday morning. Recreate must-run jobs that day, from a desk. If ops will not buy a seat, pause and email exported packs. Do not paper over Hobby with her password. There is no Grok Bot-specific spend cap and no model picker. Overflow is on-demand from model and token cost. His clicks on her login burn her pool.

Why Grok Bot needs a Cursor account is the door. Pay it for the cover. Do not lend yours.

Paste a PTO coverage charter block that names pause, cover, and no password

Standing text beats a pinned Slack message you will not reread at 16:52. Put the PTO block in the same charter the bot already rereads, next to the send rule, before the last Friday. The eight-day window below is Maren's leave. Use your own dates. The architecture does not care if the leave is three days or twenty.

PTO coverage (paste into every send-capable bot charter before last Friday)

Owner: Maren. Cover desk: Ned, only after he has his own eligible Grok Bot seat.
Window: 22 August 2026 through 29 August 2026.

Before leave (desktop app, not iPhone):
- Pause every routine on this bot. Stay until the control shows frozen.
- Pause sibling send-capable routines on other bots that share this computer.
- Do not delete this bot. Deleting a bot deletes its routines. Sessions stay.
- Copy this charter into a doc the cover can open. Export only the /workspace
  packs they need. Strip customer mail and credentials.

While out:
- Cover does not receive the Cursor password, recovery codes, or 2FA phone.
- Cover does not resume this bot from iPhone.
- Jobs that must fire live on Ned's account, on Ned's bot, with Ned as owner.
- Ned never sends as Maren. Ned never opens Maren's Gmail cookie.
- Phone app: approve steps, pause or resume a routine, read run history, delete a routine. Editing and testing wait for a desk.

On return:
- Resume only from a desktop after reading /workspace and Sent.
- Do not treat a missing history row as proof nothing happened. Individual accounts and self-serve Teams still have no audit view of Bot actions; Enterprise has audit logs and Action Recording. Check the destination.
- Offboard the cover's temporary bot on their account, not by deleting yours.

If send is even possible on the card, add one more line: send stays paused for the whole window. Inbox Triage already treats send as a human step. Borrow that boundary for the week you are not in the room.

Answer the founder who says the intern can babysit the live bot from the office

The objection is strongest when Ned is sitting ten feet away. He is trusted. He already sees the customer Slack. He has a Windows desk. Why buy a second seat when he can watch Follow-up Clerk on her laptop, or log in from the office Mac she left unlocked.

Watching does not split the home directory. An unlocked office Mac with her session is her computer. A login from his house is her computer. Two people on one user account are still one cloud computer and one cookie jar. There is no audit view outside Enterprise, so "I will look over his shoulder" is not a log. If he can resume, he can send. If he can tidy the sidebar, he can delete routines. If he can only watch, he needs exported packs and a pause that already held.

The objection wins one narrow case: Ned already owns his own eligible seat, the must-run job is already on his bot, send is off, and Maren's send-capable clocks are paused. That is the recreate path with a desk in the same room, not babysitting her live bot. If the real request is "keep answering customers in my voice for eight days," that is a human coverage problem. Do not solve it by putting Ned inside Maren's Gmail cookie. Share a grok bot is the page for an intern who asked for a named card. This page refuses the same login when the calendar says PTO.

Prove Monday's pack appeared on the cover's computer, not on the founder's

These checks can come back false. If they do, you either left the bot running or you shared a computer and called it a shift.

Plant a harmless row you will recognize. An arbitrary example: a calendar event titled "PTO coverage probe" on Ned's calendar, not Maren's, and a line in his brief that must cite it. If Monday's brief cites Maren's calendar, he is on the wrong computer. If no brief exists and you had agreed to recreate, he never got a seat, or he tried to create from iPhone. Do not grade the week from chat. If a job went silent with files half written, that is Grok Bot stalled, not a reason to DM the password.

Keep the paused bot alive rather than delete it while you are out of the building

Delete feels like a clean OOO. Deleting a bot removes its profile, conversation, and routines. It does not retract mail, sign out of Gmail, empty /workspace, or clear the cookie jar. You also destroy the twenty most recent run records per routine. The phone app can delete too, so a pocket is no safer. Do not ask Ned to delete your bots as a favor. How to delete a Grok Bot without leaving logins behind is teardown for a planned retirement. A leave is not a retirement.

Enterprise organization admins can now Terminate a member's computer; it still keeps the durable disk, and the next session starts a fresh computer on it. Do not staff PTO as if Terminate were a leave button. Do not staff PTO around the team-level ceiling on local execution either; it caps the member's own machine, not routines on the cloud computer (teams and enterprises). Pause is the verb that exists. Leave Follow-up Clerk in the sidebar, paused, charter intact, so resume on 30 August is a desk decision rather than a rebuild.

Hand this page back when the absence is a 3am page, a share request, or a pocket freeze how-to

This page stops applying when the calendar is not the problem. A send that misfires at 03:12 while you are in town is staffing for a night: who is on call. A job going wrong in a TSA line, with no PTO plan, is the click path: how to pause from iPhone. An intern who asked to borrow the research bot by name, with you still at the desk, is a handoff of text: share a grok bot.

It also stops applying when there is no live send-capable routine and no must-run clock. A draft-only fleet can sit paused without a cover seat. A missed Monday because someone deleted the owner bot last week is a routine that did not run. Companies that need a team on-call calendar and a dedicated VM per bot are describing a product Grok Bot does not ship today, and a vendor audit log ships only on Enterprise. Do not staff an eight-day leave as if it were filled.

Keep reading: Who Is On Call When a Grok Bot Misfires at 3am, How to Pause a Grok Bot From Your iPhone, How to Share a Grok Bot Without Sharing Your Computer.

Frequently Asked Questions

Can the intern keep my live grok bot running on PTO by using my login?

No. The login is the computer, not a coverage shift. All bots share one persistent cloud computer assigned to your user, not to a bot. Cookies, sessions, files, and CLI credentials go with whoever can sign in. Screens are not security boundaries. Individual accounts and self-serve Teams still have no audit view of Bot actions; Enterprise has audit logs and Action Recording. Pause send-capable routines before you leave. If a job must fire, recreate it on the cover person's own eligible seat. Changing the password on day nine does not rewind copies they made on day two.

If I pause everything, how does the cover person still run Monday standups?

They run Monday on their computer, not on yours. A routine belongs to one bot. Nothing is team-level. Buy them an eligible seat (a seat on a self-serve Cursor Teams plan is one path, checked 23 September 2026) or a qualifying trial, then recreate the standup on a bot they own, from a desktop. The phone app cannot create that routine; it needs the desktop app. If you will not buy a seat, pause and skip the bot standup. Email a human checklist. Do not paste the founder password so their Monday pack can fire.

Can I handle PTO coverage from iPhone at the airport?

You can pause. That is the documented pocket pair, with resume, and resume is the wrong leave verb. Editing and testing a routine still need the desktop app; the phone can now show run history and delete a routine. You will not create the cover's replacement routine from the jetway. If Friday's desk pause did not happen, pause every send-capable routine you can reach, stay until frozen, and write the names in Notes. Staff the last desk day for both people. An Android-only or iPad-only bag cannot recreate coverage until someone borrows a desktop.

Do routines transfer to the cover when I buy them a Teams seat?

No. Cursor Teams Standard includes Grok Bot as a per-person stamp. Each seat gets its own cloud computer. Named bots on your account do not appear in their sidebar. There is no documented move of a bot, a computer, or a routine onto another person. Max 50 routines per bot still applies on their card. Recreate must-run jobs from the charter on their seat. Leave your live send-capable bot paused, not deleted, so you can resume when you return. Confirm live prices on Cursor team pricing the morning you pay.