2026-08-28 · Guide
Move Grok Bot Work from a Personal Seat to Work
Company Gmail still opens on the founder's personal Pro+ computer the Monday after finance buys Cursor Teams, because there is no documented transfer of a named grok bot onto a work seat.
You will not find Move, Transfer, or Reassign. A named bot is a screen on one persistent cloud computer assigned to the user account, not to the bot (computer and apps). Two invoices are not two computers until they are two accounts. Paying Teams on the same Cursor user who already holds Pro+ leaves one disk. That dual-SKU trap lives on When You Hold Cursor and SuperGrok. This page is the founder who thinks the company card already moved Inbox Desk.
Copy the charter, recreate the job on the work seat, then sign leftover company sessions out of the personal computer. How to Share a Grok Bot is the intern who asked for your bot. Grok Bot on Cursor Teams Standard is the per-seat eligibility line. Stay here if you already ran company work on personal Pro+ and finance just bought Teams.
Scan the Grok Bot sidebar for a Move to Work control that does not exist
People look for Move because Google Workspace moves a mailbox when the org changes. The Grok Bot sidebar shows a named card, so the jump is that the card should follow the invoice.
The product does not document that control. Do not invent one in an ops wiki. Do not tell Willa to click Move next to Inbox Desk after the Teams seats post. Sidebar names are labels on screens, not org objects. What a Grok Bot is is a named agent on a managed cloud computer assigned to the user.
As of 28 August 2026 the model is one computer per account. None of the 11 August beta or the 21 August eligibility widening added a documented transfer of a named bot, a computer, or a routine between people. Treat a Transfer Bot screenshot as a mock until you can open the same control in the live app.
The honest sentence: I can give the work identity the job as text. I cannot give it my bot.
| What you hoped the product had | What is documented | What clicking around will actually do |
|---|---|---|
| A Move to Work control on the named card | No documented control | Nothing. Do not brief finance as if it exists |
| Reassign Inbox Desk to the company Teams login | No documented move of a bot, computer, or routine | Nothing. Recreate the job on the work account |
| Invite the work identity as a viewer of the personal bot | No documented viewer role | Nothing. The work login cannot guest your Bot screen |
| Attach the Teams invoice to the personal Cursor user and keep the roster | Possible as an anti-pattern | You still have one computer. Company and personal cookies stay mixed |
| Copy the charter into a doc the work identity can open | Text you already own | The work seat can recreate the job. It does not receive your sessions |
Write the missing button down as a product fact. Finance posted the seats. The architecture will still be one computer per account on Monday.
Count two invoices as two computers only after they are two user accounts
A personal Cursor Pro+ charge and a company Cursor Teams Standard charge look like a handoff. They are two SKUs. They are not two machines until they are two identities.
Cursor Pro at twenty dollars a month is the cheapest documented paid individual door as of the 23 September 2026 check against cursor.com/pricing. Confirm that number live. A self-serve Cursor Teams seat includes Grok Bot for every member as a per-person stamp, checked against Cursor team pricing and the Grok Bot FAQ. Confirm those figures the morning you pay. A Teams Premium seat is the same Bot product on a richer Cursor SKU, and it is not required for access. Cursor Hobby, the free plan, does not include Grok Bot, and an individual SuperGrok, SuperGrok Plus, SuperGrok Heavy or X Premium+ subscription can be linked instead.
Sign-in still runs through a Cursor account (why Grok Bot needs a Cursor account). The computer follows that identity. The FAQ is blunt about a related case: if you have both a Cursor and a SuperGrok subscription, Grok Bot uses whichever has more usage. Two eligible charges do not mint two computers.
If you wanted two computers, you needed two eligible user accounts. Same human, two logins, two computers. Same human, two invoices, one login: one computer. Privacy Mode (Legacy) blocks Grok Bot entirely. A correct Teams invoice will not save a work identity that still sits in Legacy (Grok Bot and Privacy Mode).
Keep the personal Pro+ computer alive until the work Cursor identity is a real login
Do not cancel personal Pro+ on the afternoon the company card posts. Do not delete Inbox Desk before the charter is in a document you own. The personal computer is still the only place the standing job exists until the work identity has a roster, a charter, and a clock that actually fired.
The work login needs its own eligible stamp. A Teams seat assigned to someone else does not activate Grok Bot for Willa. Sign-in knows the plan. The installer does not. Eligibility widened on 21 August 2026 (xAI announcement).
Do the move from a Mac, Windows, or Linux desk. 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 the Linux desktop client. From the phone app (iPhone or Android) you can approve steps and pause or resume a routine, but not edit it. Editing and testing a routine still need the desktop app; the phone can now show run history and delete a routine (mobile).
Keep personal Pro+ until the work account screen prints an eligible Teams SKU, the named job exists, and one routine has a run record you opened. Cancelling the individual line while company Gmail still lives on that computer is what survives if you drop Grok Bot, not a seat move.
Copy standing instructions into a document you own before the company seat exists
Open the personal bot while it still exists. Copy the charter markdown into a file you own. Export any /workspace pack the work job will need as a dated file. Strip customer mail, payroll PDFs, and credentials that should never have sat next to a research screen.
You are copying text. You are not cloning a computer. Cookies, sessions, files, and command-line credentials stay on the personal VM. Hosted MCP sign-in tokens stay with Cursor's backend, not on the computer (teams and enterprises). They will not appear on the work identity. Reconnect hosted tools on the work Cursor account, or skip them if the job can live on files you already exported. Where Grok Bot MCP sign-in tokens actually live is the location page.
A listing paste is a ceiling, not a live clone. Inbox Triage and Chief of Staff Briefing give the work seat a job shape and a boundary. They do not give it the personal Gmail cookie. How to write a Grok Bot charter is the template if the personal bot never had standing text.
Do this before you sign into the work identity on the same laptop. Switching Cursor users mid-copy is how people lose the chat they were about to paste. Individual accounts and self-serve Teams still have no audit view of Bot actions; Enterprise has audit logs and Action Recording. The product will not reprint last month's instructions after you close the personal roster.
| Item on the personal computer | Lives where | Moves if you copy the charter | Survives if you later delete the personal bot |
|---|---|---|---|
| Charter markdown | Standing instructions on that named bot | Yes, if you paste it into a doc you own | No. Copy first |
| /workspace packs | Shared disk on the personal computer | Only the files you export by hand | Yes, until you delete the files |
| Browser cookies for company Gmail, Notion, Linear | Shared browser on the personal computer | No | Yes. Delete does not sign them out |
| CLI credentials and API keys | Shared home directory | No | Yes |
| Routines and the 20 most recent run records | Glued to that named bot | No. Max 50 routines per Bot. Nothing is team-level | No. Deleting a Bot deletes its routines |
| Hosted MCP grants | Cursor backend on the personal identity | No | Yes, until you revoke in settings |
Copy first. Recreate second. Sign out third. Delete last, and only if the personal job is actually finished.
Recreate each named job on the work seat as a blank screen with no cookies
Sign into Grok Bot as the work Cursor user. Confirm the account screen prints Teams Standard, Teams Premium, or another eligible stamp. Create a new named bot. Paste the charter. Connect the minimum company tools on this computer, not the maximum.
The new screen is empty. It does not inherit the personal cookie jar. That is the point. Company Gmail has to be signed in again, on the work computer, as the company mailbox. Personal Gmail stays off this machine. Least privilege for bots is the grant list. Do not use separate bots as a sandbox still applies: every bot on the work account will share the work computer. Do not park a personal GitHub CLI next to the company inbox bot just because both belong to Willa.
All bots on the work account share one persistent cloud computer assigned to that work user, not to an individual bot. Each bot gets a screen. Screens are work surfaces, not security boundaries. The vendor line is on approvals, security and privacy: do not use separate Bots as a security boundary. Deleting a bot later will not remove shared-computer files or browser sessions.
Static egress IPs apply. Some services flag datacenter addresses. Complete 2FA on the Agent Computer, never in chat (Grok Bot hit a 2FA prompt). An approval controls the proposed action. It does not reverse work already completed.
Do not substitute a ten-minute demonstration for the charter. Teach-by-demonstration records visible computer interaction for up to ten minutes, no microphone audio, produces a draft skill, browser workflows only, and is unavailable on iPhone. It will not copy cookies. It will not copy routines. Paste the text.
Rebuild weekday clocks on the work bot because personal routines never migrate
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. That paragraph is from skills, routines and automations, and it survives every Teams invoice.
There is no org object named Monday Inbox that outlives the personal card it was glued to. Copying Inbox Desk into the work sidebar as a name is not a move. Recreate the routine on the work bot. How to schedule a Grok Bot routine is the clock page.
Leave the personal routine running until the work clock has a run record you opened. Then pause the personal clock. If you pause first and the work recreate slips a day, company Gmail goes dark for a weekday. If you never pause, two computers draft the same inbox. Two drafts is messy. Two sends is an incident.
On iPhone you can pause the personal routine if you are already out the door. You cannot rebuild the work clock from the phone. Sit at a desk. Twenty run records is not an audit log. If you need last month's evidence, export the pack files from the personal /workspace before you cut that bot. The work computer starts at zero.
Follow Willa from five months of personal Pro+ onto the company Teams seat
This is an invented worked example, not a customer story. Willa, Oakrelay, and the counts below are arbitrary choices for the walkthrough.
Willa founded Oakrelay, a nine-person ops tooling shop. From late March 2026 she paid Cursor Pro+ herself at sixty dollars a month because the company had no Teams seats. She ran three named bots on that personal account: Inbox Desk on company Gmail, Morning Brief on calendar plus mail, and a churn watcher fed from a CRM export. Two weekday routines. Four vendor sessions on the shared personal browser: Gmail, Notion, Linear, HubSpot. Personal GitHub sat on the same computer because it was her laptop and her Cursor user.
On 24 August 2026 finance bought nine Cursor Teams Standard seats. Someone in Slack wrote: Willa's bots should just show up under the company login now.
On 25 August 2026 at 09:10 she signed into Grok Bot with Willa@oakrelay. The sidebar was empty. She scanned for Move, Transfer, Reassign. Nothing. At 09:28 she almost added the Teams seat onto her personal Cursor user so the roster would stay. That would have been two invoices, one computer. Company Gmail would have stayed next to personal GitHub. Offboarding later would have been a person-delete that also killed her personal mail bot.
She did not attach the seat. She copied three charters into an Oakrelay doc, exported two /workspace packs, and created Inbox Desk, Morning Brief, and Churn Watch on the work identity. She signed company Gmail into the work computer. She rebuilt the two weekday routines. At 16:40 the work Inbox Desk had one run record.
She did not sign company Gmail out of the personal computer. She had a dinner. She told herself the personal bot was just sitting there.
On 26 August 2026 at 07:12 the personal Inbox Desk routine still fired. It opened company Gmail without a login prompt, because Monday's cookie was still in the personal browser. The work Inbox Desk also fired. Two drafts of the same seven threads landed in two folders. Nobody sent. The failure was the leftover session, not a missing transfer button.
| Clock | Move | What Willa believed | What actually moved |
|---|---|---|---|
| 24 Aug, afternoon | Finance posts nine Teams Standard seats | The company now owns Inbox Desk | The company now owns nine eligibility stamps |
| 25 Aug, 09:10 | Work login, empty sidebar | The roster should have followed the invoice | Named bots live on the personal account computer |
| 25 Aug, 09:28 | Draft: attach Teams to personal Cursor, unsent | Keep the cookies, skip recreate | One computer, mixed cookies, fake handoff |
| 25 Aug, 11:20 | Three charters copied, two packs exported | A transfer of the bots | Text and documents. No cookies, no routines |
| 25 Aug, 16:40 | Work Inbox Desk exists, one run record | The move is finished | The work job exists. The personal cookie still exists |
| 26 Aug, 07:12 | Personal routine opens company Gmail | The old bot is idle | Leftover session. Two computers drafted one inbox |
The dated failure is 26 August 2026 at 07:12, not 25 August at 09:10. Empty sidebar is expected. A leftover company cookie on the personal computer after the work roster is live is the miss this page exists to catch.
Sign company vendors out of the leftover personal computer after the work roster is live
The work recreate does not log the personal computer out. Deleting the personal named bot does not either. Logout is a person at the vendor, on the Agent Computer that still holds the cookie.
Sit on the personal identity. Open the shared browser. Sign out of company Gmail, company Notion, company Linear, and company HubSpot until each URL shows a login prompt. Then revoke OAuth on each vendor's current apps page. Rotate any API key the personal bot could have read. Sweep company CSVs out of the personal /workspace so a remaining personal bot cannot open them.
Hosted MCP grants on the personal Cursor user stay with Cursor's backend. Signing the vendor out of the browser does not pull them. Revoke those in personal Cursor settings.
Rotate vendor access after a bad Grok Bot incident is the incident version of this list, for when a sibling bot already loaded a console it should not have. This page is the planned leftover: you meant to leave the personal computer, and the cookie stayed. How to delete a Grok Bot without leaving logins behind is the sidebar click after the vendors are dark. Admin Terminate, Enterprise only and for organization admins only, deletes a member's computer but keeps the durable disk. Do not treat Terminate as a transfer tool. It would not move the bot onto the work seat anyway.
Keep personal vendors on the personal computer if you still want a personal job there. Sign out the company ones. Mixing them is how Inbox Desk on a personal seat keeps drafting Oakrelay mail in September.
Freeze every personal routine that still opens a company mailbox or CRM
Pause is not delete. Pause freezes future work. It does not recall a draft that already landed, and it does not sign anyone out.
After the work clock has a run record, pause every personal routine that still talks to company Gmail, company calendar, company CRM, or company Slack. Stay until the control shows frozen. Do this at a desktop if you also need to edit. iPhone can pause if that is all you have in the moment (how to pause a Grok Bot on iPhone).
Leave personal routines that talk only to personal mail or personal calendar. The whole point of two accounts is that personal work can stay personal. You are not required to burn the Pro+ computer. You are required to stop using it as a shadow company seat.
If a personal routine cannot be paused because you are on a train, pause from iPhone and finish the vendor sign-out at a desk the same day. A paused routine plus a live cookie is still a live cookie. A sibling personal bot can open the tab. Screens are not a wall.
Do not delete the personal Inbox Desk until the charter is copied, the work job has fired, the personal routine is paused, and company vendors show a login wall on the personal computer. Delete last. Delete is a profile cut. Sessions stay (delete a Grok Bot safely).
Prove the personal computer cannot open company Gmail without a fresh login prompt
These checks can come back dirty. If they do, you recreated a job and left a company identity on the personal disk.
| Check | Pass | Fail |
|---|---|---|
| Work sidebar shows Inbox Desk you created, and personal sidebar still shows its own Inbox Desk or a paused leftover | Two accounts, two computers | You are looking at one laptop session, or you attached Teams to the personal user |
| A remaining personal bot cannot open company Gmail, Notion, Linear, or HubSpot without a login prompt | Company sessions left the personal computer | A cookie remained, or you never signed out |
| The work bot cannot open personal Gmail or personal GitHub without its own sign-in | Personal sessions did not leak onto the work computer | You signed a personal account into the work browser just this once |
| Ops can name the SKU on the work account (Teams Standard, Teams Premium, Ultra, or another eligible stamp) | The work identity is eligible without the personal login | Hobby, or a SuperGrok that was never linked, papered over with the personal password |
| The work routine has a run record you opened, and the personal company-facing routine is frozen | Clocks split by identity | Both still fire, or only the personal one still fires |
| Hosted MCP on the personal Cursor user is revoked for company servers, or listed as unused | Backend grants match the leftover plan | A personal grant still calls a company tool |
Ask a remaining personal bot, not the one you are about to delete, to load the company Gmail URL. Pass is a login wall. Fail is the inbox, a staff name in the corner, or yesterday's thread list. Do not ask the work bot to reopen personal Gmail to confirm isolation. That mints a fresh cookie on the wrong computer.
If the Grok Bot FAQ and this page disagree, the FAQ wins. Dates on this page are 24 to 28 August 2026, with plan facts rechecked 23 September 2026. There is no Grok Bot-specific spend cap beyond the account On-demand monthly limit, and no model picker. Confirm eligibility on the live invoice the morning you argue with finance.
Answer the founder who says the company invoice already moved the named bots
The objection is strongest when Willa is the company. She is the founder. She is the Cursor buyer. She is the person who will sit in both chairs for years. Why recreate three bots and sign out four vendors when the company is now paying, and the personal Pro+ line can simply become a Teams line on the same user.
Because the product isolates by user account, not by who paid. Attaching Teams to the personal Cursor user keeps one computer. Company Gmail stays next to personal GitHub. Routines stay on that computer. Offboarding, if she ever leaves or if a co-founder needs a clean company machine, becomes a person-delete that also destroys her personal roster. Two invoices are not two computers until they are two accounts.
The objection wins one narrow case: there is no company identity and there will never be one. A true one-person shop that will never hire, never take a co-founder, and never need a work-owned computer can keep running on personal Pro+ and stop reading this page. That setup is how to build a one-person company with Grok Bot. The moment finance wants a company seat they can assign, pause, or delete without touching her personal mail, you are back on this page. Recreate. Then sign the leftover personal sessions out.
Saving an afternoon by skipping recreate is how 26 August 2026 at 07:12 happens. Two drafts. One leftover cookie. No transfer button to blame.
Paste a seat-move charter that names both computers and forbids a transfer click
Standing text beats a Slack message you will not reread when the next Teams seat posts. Put this block in every company-facing bot you recreate on the work identity, and in every leftover personal bot until company vendors are dark. Change the names. Keep the stop list.
Seat move (paste into company bots on the work identity, and into leftover personal bots)
Owner on work: Willa at Oakrelay, Cursor user Willa@oakrelay, Teams Standard seat.
Owner on personal: Willa, Cursor user on personal Pro+. Different account. Different computer.
There is no Move, Transfer, or Reassign control. Do not wait for one.
Copy this charter. Recreate the job on the work seat. Then sign leftover
company sessions out of the personal computer.
Work computer (this bot, if you are the work Inbox Desk):
- You draft from company Gmail only. You never send.
- You never sign into a personal mailbox, personal GitHub, or personal bank.
- You never complete 2FA in chat. 2FA happens on the Agent Computer, then a human signs the vendor out if the job was a one-time export.
- You never describe delete as a session close.
Personal computer (leftover bots, until company vendors are dark):
- Pause every routine that opens company Gmail, Notion, Linear, HubSpot, or company Slack.
- Do not fire a company weekday clock after the work clock has a run record.
- Company vendors must show a login prompt. If they load as staff, the move is not finished.
Never:
- Attach the company Teams invoice to the personal Cursor user and call that a move.
- Share the personal Cursor password with a teammate so they can see the old bots.
- Treat a listing paste as a live clone of cookies, routines, or run records.
- Complete a 2FA prompt you did not plan, on either computer.
If a control named Move to Work appears, ignore it until the live FAQ documents a transfer of a named bot between accounts. As of 28 August 2026 that transfer is not documented.
Inbox Triage already treats send as a human step. Borrow that boundary for both computers. Chief of Staff Briefing is the morning pack that should live on the work seat once calendar and mail are company-owned. Do not keep the briefing on personal Pro+ because it already knows the sources. It knows them because of a cookie you have not signed out.
Stop this page when the problem is two SKUs on one login, not two logins
This page stops when the work identity exists, the job has been recreated, and the personal computer cannot open company vendors without a fresh login. It does not own the dual-SKU usage pool. It does not own the Teams line item. It does not own an intern who asked for your bot by name.
If both a Cursor charge and a SuperGrok charge already sit on one human and you think that isolated work from home, leave. That is When You Hold Cursor and SuperGrok. Two invoices are still one computer. This page will not unsay that.
If you are buying Teams and have no personal roster to move, leave. That is Grok Bot on Cursor Teams Standard. You are stamping people, not migrating bots.
If someone wants to run your named bot without becoming a second account, leave. That is How to Share a Grok Bot. Share output. Do not share the login.
If the leftover is already an incident (a research bot loaded a company console), leave. That is rotate vendor access. If you are cancelling Pro+ entirely, leave. That is what survives if you drop Grok Bot.
Park intern sharing, the Teams SKU, and dual-house billing on their own pages
The architecture under all four pages is the same: one computer per user account, screens are not security boundaries, cookies survive delete, routines die with the bot, nothing is team-level. The procedure differs.
Share is a teammate who wants your card. Teams Standard is finance buying eligibility. Both-subscriptions is two houses on one identity. This page is a founder who already ran company work on personal Pro+ and now has a work seat. Copy the charter. Recreate on the work seat. Sign leftover personal sessions out. There is no transfer button.
The team-level ceiling on local execution that team admins can now set, and the Enterprise admin Terminate that deletes a member's computer but keeps the durable disk, are not a migrate-to-work tool. Do not lean on them. Do the recreate this week from a desktop.
Confirm live prices and the live FAQ the morning you brief finance. Eligibility moved on 21 August 2026. The in-product entitlement wins over a screenshot in Slack.
Keep reading: When You Hold Cursor and SuperGrok, Grok Bot on Cursor Teams Standard, How to Share a Grok Bot.
Frequently Asked Questions
Is there a button to transfer a named Grok Bot from a personal seat to a work seat?
No documented control exists. There is no Move, Transfer, or Reassign on the named card, and neither the 11 August 2026 beta nor the 21 August eligibility widening added a documented transfer of a bot, a computer, or a routine between user accounts. All bots on an account share one persistent cloud computer assigned to that user, not to a bot. Screens are not security boundaries. Copy the charter as text, create the job on the work identity, and rebuild routines there. Confirm the live FAQ if you think a transfer path shipped after 28 August 2026.
If the company buys Teams, do my personal Pro+ bots appear on the work login?
No. A self-serve Cursor Teams seat includes Grok Bot for every member as a per-person eligibility stamp, checked as of 23 September 2026. The work login is a different user account with its own cloud computer. Named bots that live on the personal Pro+ account do not appear in the work sidebar. Recreate each job from the charter. A Teams Premium seat is the same Bot product on a richer Cursor SKU, still without a transfer button, a model picker, a Grok Bot-only spend cap, or an audit view of Bot actions, which is Enterprise only.
Can I attach the Teams seat to my personal Cursor account and skip the recreate?
You can attach a second eligible SKU to one Cursor identity, and Grok Bot will keep using that one computer. Two invoices are not two computers until they are two accounts. If the company needs a work-owned machine they can delete when the founder leaves, the work identity has to be a separate login. Attaching Teams to personal Pro+ leaves company Gmail cookies next to personal GitHub on the same disk. The dual-SKU usage rule is the both-subscriptions page. This page is the seat-move. Do not skip recreate to save an afternoon.
What do I do with leftover sessions on the personal computer after the work bots are live?
Sign the vendors out on the personal Agent Computer until you see a login prompt, then revoke OAuth at each vendor. Deleting the personal named bot does not remove shared-computer files or browser sessions. Hosted MCP tokens stay with Cursor's backend, so revoke those in personal Cursor settings. Pause personal routines that still talk to company tools before you call the move finished. Prove the leftover by asking a remaining personal bot to load company Gmail. Pass is a login wall. Fail is the inbox. Confirm those labels on the vendor page.