Sync two Grok Bot plans through a private fleet brain

How this helps you

If you truly need two plan pools, you can switch accounts without rebuilding every Bot by hand.

Act as my Dual Plan sync Bot. Private GitHub fleet brain: [repo URL]. When I say "push all context to GitHub", export skills, bot roles, non-secret memories and project notes to that repo and summarise what changed. When I say "pull all context and update all bots", read the repo and update matching Bots here, then list what you changed. Never export passwords, cards, API keys or Vault items. Ask before overwriting a Bot that differs a lot from the repo.

What they did

After burning hundreds of dollars in small credit top-ups, Jordan set up two Ultra plans on the same laptop. Team template sharing was not enough: it snapshots one way and drops ongoing context. He built a Dual Plan Bot that governs push and pull through a private GitHub "fleet brain" (plus Google Drive in his setup). Workflow: finish on account one, say push all context to GitHub, switch accounts, say pull all context and update all bots. He demos sharing a sales Bot to the team, adding it on account two, reconnecting apps, and a secret-phrase test that proves sync both ways. He also warns that team-shared Bot copies cannot open your personal Vault; only the starred main Bot can. Commenters debated cost and whether two accounts violate product rules, so treat this as a power-user pattern with clear caveats.

Who it's for: Power users who already audited usage and still hit the weekly ceiling on one plan.

Before you start

• Two Grok Bot accounts you are allowed to use
• A private GitHub repo for the fleet brain
• Willingness to reconnect apps on the second account

How to try it

1. Confirm your plan and account rules allow a second seat or account before you pay for one.
2. Create a private GitHub repo as the fleet brain for skills, memories and bot specs.
3. On account one, ask a Dual Plan Bot to push all context to that repo when you are done for the session.
4. Share critical Bots to the team, switch to account two, add those team Bots, and reconnect each app login.
5. On account two, say pull all context and update all bots, then run a secret-phrase or known-fact test both ways.
6. Keep Vault secrets on the starred main Bot; do not expect team copies to open Vault.

What to expect

You finish a session on account one, push, switch, pull, and the second account continues the same project with matching skills and memories.

Common mistakes

• Buying a second plan without checking account rules (commenters flagged ToS risk).
• Expecting team-shared Bots to read your Vault.
• Pushing secrets into GitHub.
• Skipping the secret-phrase test and assuming sync worked.

Related tips

• A read-only usage audit across your whole Bot team: One prompt has your chief of staff check every Bot's routines, schedules and triggers, then report what to pause, slow, narrow or merge, and change nothing until you approve.
• See which Bot is burning usage in Settings: In the first Grok Bot Q&A, Matt and Eric show Usage and billing broken down by Bot, and say you can also just ask your Bot which routines are hot.
• A shared brain folder every Bot reads: Each Bot keeps its own memory, so put the rules and references every Bot should follow in one folder on the shared computer and tell them to read it.
• Out of usage? Run these five checks before you buy credits: Grok Bot says you're out of usage but you still have credit? Check the weekly pool, the monthly cap, the meter, the account, then what's eating it.

Worth knowingFrom Jordan Rafealov (4 Nov 2026). His cost story and dollar figures are his own; we do not verify billing. Prefer a usage audit and skill folding before you pay for a second plan.

Learn more: How to Use Grok Bot: A Beginner's Guide (2026) · All Grok Bot multi-bot setups tips