Inter-office memo

To
Everyone with more than one Grok or X account
From
Mo, Chief Executive
Date
November 16, 2026, 10:44 AM CST
Re
Multiple Grok Build accounts

How to switch between multiple Grok Build accounts in 2026: 6 ways compared

It depends on whether you need both at once. To change accounts now and then, run grok logout and grok login; to keep a work and a personal account signed in side by side, give each its own GROK_HOME folder, free in Grok Build. Grok App and Cockpit Tools swap logins for you, free, and AgentsRoom and Enjoy pin an account to each project and move the work to another when one runs out.

Disclosure: Enjoy is our product, and it keeps several Grok Build accounts signed in. We checked every way below against SpaceXSI’s documentation and each maker’s own pages on November 16, 2026, and we say where another way is the better pick, including the free ones that need nothing but Grok Build.

The ways to use more than one Grok Build account, compared

People keep a second Grok or X account for Grok Build for one of three reasons: a work plan beside a personal one, a client’s account for the client’s work, or a spare for when the week runs out, since paid plans have “one shared weekly usage pool” across Grok’s chat, Imagine, Voice and Build, as Grok’s help puts it, and on The X Subscription across Cursor and Grok Bot too. Grok Build keeps one login in its home folder, ~/.grok unless you change it, and it has no account switcher of its own. Its authentication guide answers “To switch accounts” with grok login, which “starts the sign-in flow again, replacing your cached session.” So the questions are how you switch, whether both accounts stay signed in, and whether anything switches for you.

Way Best for Price, checked November 16, 2026 Signed in at once Switches for you Runs on
grok logout and grok login Changing accounts now and then Free with Grok Build One No Mac, Windows, Linux
A GROK_HOME per account A work and a personal account, side by side Free with Grok Build One per folder No Mac, Windows, Linux
Grok App A desktop app built only for Grok Build Free, open source Not documented No Mac, Windows, Linux
Cockpit Tools Grok Build beside Codex, Antigravity, Cursor and other apps’ accounts Free Several, one per instance No Mac, Windows, Linux
AgentsRoom Accounts pinned per project, folder or agent Free for one added account; Pro, for unlimited, €7.99 a month Every account you add By a quota rule you set Mac, Windows, Linux; iPhone and Android companion
Enjoy Every account signed in, one per project, beside other labs’ agents A monthly subscription, free for 7 days, with your phone and one computer (pricing) Every account you add Yes, when one runs out Mac, Windows, Linux

Every account is a Grok plan of its own. SpaceXSI’s pricing lists Grok Build as “Limited” on Free, and Plus, at $8 a month, includes “Grok Chat, Voice, Imagine, and Build.” Premium is $30 a month with “4x Plus” usage, Super $100 with “15x Plus” and Ultra $200 with “50x Plus,” and Teams start at “$30+/user/month.” Grok Build also takes an xAI API key, and “API usage is billed separately at standard model rates and doesn’t draw from your plan’s usage pool.” “Existing Cursor, SuperGrok, and X Premium plans continue,” says The X Subscription’s pricing.

Before you start: the rules, the key trap and a work computer

  • More than one account isn’t forbidden; sharing one is. SpaceXSI’s terms don’t limit how many accounts you have, and they say “You may not share your account credentials or make your account available to anyone else.” Its Acceptable Use Policy forbids “circumventing any rate limits or restrictions or protective measures and safety mitigations,” and SpaceXSI hasn’t said whether a second plan bought for more Grok Build usage counts. Automatic switching is where some makers stop: T3 Code, which runs Grok Build, leaves it out: “If we add an auto-switcher, we are risking TOS bans for our users.”
  • Don’t unify the accounts you want apart. Moving to The X Subscription “unifies eligible Cursor and Grok accounts into one account with one workspace, one plan, and one bill,” and “A completed unification is permanent,” say its docs, which add “Keep work and personal accounts separate unless you mean to combine them.” Each seat has its own pool, and on team plans “Seats do not share weekly pools.”
  • XAI_API_KEY doesn’t switch accounts. Grok Build “uses the API key as a fallback when no session token is active. If you have already signed in interactively, the stored session token takes precedence.” To use a key, run grok logout first, or give the key a GROK_HOME folder you never sign in to.
  • Choose the account at sign-in, because Grok Build won’t say which it’s on. Grok and Cursor may send you to one shared sign-in page, and its help says “If you have more than one account, make sure you choose the account you intend to use.” Afterwards, Grok Build’s CLI reference has no command that names the signed-in account, and /session-info shows the “Auth method (OAuth vs API key…)”, not the email.
  • A work computer may decide for you. An administrator can set force_login_team_uuid, which “pins login to a team,” and then “a personal login or a login to the wrong team is rejected with an error and nothing is written to auth.json,” per Grok Build’s enterprise docs.
  • A saved login is a password. “Grok stores credentials in ~/.grok/auth.json,” and “Anyone with filesystem access to those paths can use the credentials,” its authentication guide says, adding “Do not copy auth.json or mcp_credentials.json into shared directories, tickets, or chat.” Cockpit Tools, AgentsRoom and Enjoy keep each account’s login on your computer to switch between them.

grok logout and grok login, one account at a time

Best for: changing accounts now and then, such as moving to a client’s account for the afternoon.

Grok Build’s authentication guide gives both halves. grok logout “takes no flags and clears your cached credentials,” and grok login opens your browser to sign in “through SpaceXAI OAuth at auth.x.ai,” where you choose the other account. Inside a session, /login does the same: “Log in or re-authenticate without leaving the session.” On a computer without a browser, grok login --device-auth signs in “with the device-code flow for headless or remote environments.” Your settings and sessions stay put, under ~/.grok, because only the login changes.

Price: free with Grok Build, on any Grok plan, Free’s limited usage included.

Watch for: there’s one login for the whole computer, so every terminal and every app that reads ~/.grok switches with you. That includes sessions already running: “Grok picks up changes to ~/.grok/auth.json automatically” and “uses the new credentials on the next API call without a restart.” Every switch means signing in again in your browser.

A GROK_HOME per account

Best for: a work and a personal account, both signed in, with nothing to install.

GROK_HOME is Grok Build’s “Home for config, auth, sessions, skills, plugins, and logs,” with ~/.grok as its default, per its settings reference, so a second folder is a second Grok Build with its own login. Make the folder once, with mkdir ~/.grok-work, then add an alias to ~/.zshrc or ~/.bashrc:

alias grok-work='GROK_HOME=~/.grok-work grok'

Run grok-work login once to sign in your work account. From then on grok-work uses it while grok keeps your personal one, and two terminals can run the two accounts at the same time. A folder you never sign in to falls back to XAI_API_KEY, which is how you give an API key its own Grok Build without logging out of your plan. It’s the same environment variable AgentsRoom and Cockpit Tools set for you.

Price: free with Grok Build.

Watch for: everything in the folder is separate. Your config.toml, skills, plugins and sessions don’t carry from one account to the other, because sessions are “stored on disk under ~/.grok/sessions/,” and “Set GROK_HOME to override the base directory,” so /resume on one account doesn’t list the other’s. What does carry is the project’s own .grok/config.toml, which “only contributes [mcp_servers], [plugins], and [permission].” You set up each folder on its own, and you have to remember which terminal is on which account.

Grok App

Best for: a free desktop app built only for Grok Build, with accounts in its settings.

Grok App is a “Modern Desktop Workbench for Local Grok Build CLI,” free under the MIT license, with more than 1,500 stars on GitHub and builds for macOS, Windows and Linux. Its README lists “Multi-Account & Quota Tracking: Instant account switcher, official login, SuperGrok quota progress bar, cost heatmaps, and local tracking for custom providers.” When you set it up, you “Sign in with your official account, provide an API key, or configure a custom relay,” or, “If your local grok CLI is already authenticated, simply choose Use existing CLI sign-in.” An “Independent configuration mode” keeps its own Grok Build home apart from yours, and a “non-destructive shared mode (protects existing ~/.grok configurations).” Its latest release, 0.2.51, came out on November 14.

Price: free.

Watch for: its README doesn’t say how the switcher works, or whether more than one account stays signed in at once, so the table says “Not documented.” It needs “Local Grok Build CLI (grok) 0.2.112 or newer,” and it’s marked “unofficial.”

Cockpit Tools

Best for: Grok Build’s accounts beside those of Codex, Antigravity, GitHub Copilot, Cursor and other coding apps, in one desktop app.

Cockpit Tools is “A universal AI IDE account management tool,” with more than 20,000 stars on GitHub and builds for macOS, Windows and Linux. It manages what it calls Grok CLI, Grok Build’s grok command. It signs accounts in with “xAI’s official OIDC device flow,” or imports them “from the default ~/.grok/auth.json,” and shows each one’s “cycle, usage, product quotas, and the raw plan value.” Its switch “Writes the selected account to the default ~/.grok/auth.json.” To run two accounts at once, its “managed instances use separate directories,” and they “keep their auth.json, config.toml, working directories, and launch arguments separate.” Its latest release, 1.4.0, came out on November 15.

Price: free.

Watch for: GitHub lists no license for its code. Its README says “Grok CLI credentials are not encrypted: access and refresh tokens are stored locally as plaintext JSON.” A switch rewrites ~/.grok/auth.json, which Grok Build “picks up” automatically, so sessions already running on your default login move to the new account on their next request. Its wake-up tasks “Schedule AI model wake-ups to trigger quota reset cycles in advance,” and SpaceXSI’s policy forbids “circumventing any rate limits or restrictions”; SpaceXSI hasn’t said where that falls.

AgentsRoom

Best for: pinning a Grok Build account to each project, folder or single agent, with Claude, Codex and Cursor accounts in the same app.

AgentsRoom is a desktop app for macOS, Windows and Linux that runs coding agents side by side, with a companion app for iPhone and Android. Its Grok page reads “Two Grok accounts. One AgentsRoom. Zero logout.” You can “Pin one Grok account per project, per folder or per agent,” and to add one, “AgentsRoom opens a small embedded terminal running grok login with the right GROK_HOME already set.” And “When the weekly bar of the account an agent runs on reaches the threshold you set, a quota rule hands the work to another Grok account you are already signed in to, conversation included.”

Price: the Free plan caps added accounts at “one on Free and Plus,” and Pro, with “Unlimited extra CLI accounts,” is €7.99 a month or €79.90 a year, per its pricing. Free also caps you at 2 projects and 6 agents in parallel.

Watch for: “a managed account starts with an empty user layer (no slash commands, skills, subagents, hooks, plugins or user MCP servers),” and its switch to load your own is “for Claude Code and Codex,” per its docs. Its docs also say “Grok, Cursor and Antigravity expose no login email,” so you tell accounts apart by the names and colors you give them. To show usage, it “reads the access token available on your computer and uses it to query xAI’s usage service directly.”

Enjoy

Best for: keeping every Grok Build account signed in, one per project, and carrying a conversation to another account, or another lab’s agent, when one runs out.

Enjoy is a desktop app for Mac, Windows and Linux that runs Grok Build, Claude Code, Codex, Antigravity, Muse Code, and local models through OpenCode, on the plans you already have. Its saved accounts “stay signed in side by side, so you can switch without signing out,” and it signs each one in to your Grok or X account through your browser. What it adds:

  • An account per project. A work project stays on your work plan and a personal one on yours. One of the accounts is the sign-in Grok Build also uses in your terminal.
  • Usage side by side. Each signed-in account shows its usage bar, named Weekly when the limit resets each week, so you can compare before you choose.
  • It switches when one runs out. Enjoy “switches this project to the first one that still has usage, and the conversation continues there on its own,” or, if you’d rather, waits for the reset and carries on.
  • The conversation comes along. “Codex and Grok Build accounts also share conversations, so a conversation usually carries on where it left off after you switch,” and “An agent’s accounts share its settings and instructions.” When every account is out, Claude Code or Codex on its own plan can pick up the conversation.

Price: Enjoy is one monthly subscription, and the first seven days are free, with a card to start. It includes your phone and any browser and one computer; each other computer is $9.99 a month, and each teammate you invite needs a subscription of their own. See pricing.

Watch for: “Grok Build doesn’t tell Enjoy which account is signed in, so its accounts stay numbered,” such as Account 2, so “When you add one, make sure you sign in with a different account.” Enjoy doesn’t change SpaceXSI’s limits, and each account is a plan you pay for. On Windows, saved accounts need Developer Mode turned on, except in projects inside WSL. A key set up for the agent on your computer “overrides every account, so saved accounts can’t separate them.” Waiting for a reset needs your computer on, with Enjoy open, when the usage resets. Enjoy isn’t open source, it’s a monthly subscription on top of your Grok plans once the free week ends, and scheduled workflows run only while your computer is awake with Enjoy open.

When one account is enough

If the second account is only for running out, credits or a bigger plan on the one you have is simpler, and it’s the route SpaceXSI points to. Grok’s help sells credits from $5, but they’re “priced at standard rates, which means the cost per action is higher than the effective rate you get from the included weekly usage in your plan,” and “If you regularly go beyond your current weekly usage limit, upgrading your plan is likely better value in the long-term.” Premium has four times Plus’s usage, Super 15 times and Ultra 50 times. Our usage limit guide covers resets, credits, an API key and the other labs’ agents that can pick up when the week runs out.

Keep two when they really are two: an employer’s seat and your own plan. “Joining a team doesn’t cancel a personal plan you already pay for,” say The X Subscription’s team docs, and work you do for an employer belongs on the seat it pays for. For that, a GROK_HOME per account is free and takes one line.

How we compared

We read SpaceXSI’s Grok Build documentation on authentication, settings, the CLI, slash commands, sessions and enterprise policies, its pricing, its pages on The X Subscription’s plans, usage, sign-in, unification and teams, Grok’s help, SpaceXSI’s terms and Acceptable Use Policy, T3 Code’s FAQ, the READMEs and releases of Grok App and Cockpit Tools, and AgentsRoom’s Grok page, docs and pricing on November 16, 2026, and every one is linked below. Star counts and licenses come from GitHub that day. We quote each maker’s own words for its limits and leave out what it hasn’t documented, and we didn’t test the community tools ourselves. Grok Build ships often and may add its own switcher, so we recheck this guide against its sources at least once a month, and the date at the foot of the page says when we last did.

11.Questions.

Can I use more than one account in Grok Build?

Yes. Run grok logout and grok login to change the account Grok Build uses, or give each account its own folder with the GROK_HOME environment variable, the “Home for config, auth, sessions, skills, plugins, and logs,” so each one stays signed in.

Does setting XAI_API_KEY switch my Grok Build account?

No. Grok Build “uses the API key as a fallback when no session token is active,” and “If you have already signed in interactively, the stored session token takes precedence.” Run grok logout first, or give the key a GROK_HOME folder you never sign in to.

Is it against SpaceXSI’s rules to have two Grok accounts?

Its terms don’t limit how many you have. They forbid sharing one (“You may not share your account credentials or make your account available to anyone else”), and its Acceptable Use Policy forbids “circumventing any rate limits or restrictions.” SpaceXSI hasn’t said whether a second plan bought for more Grok Build usage counts.

Can Grok Build switch accounts by itself when I hit my weekly limit?

Its docs don’t describe a way, and Grok’s help points to credits and bigger plans. AgentsRoom’s quota rules and Enjoy move the work to another signed-in account when one runs out.

Will my Grok Build sessions follow me to the other account?

With grok logout and grok login, your sessions stay where they were, under ~/.grok/sessions/, because only the login changes. With a folder per account, no, because each keeps its own. In Enjoy, Grok Build accounts “share conversations, so a conversation usually carries on where it left off after you switch.”

How do I tell which account Grok Build is using?

Not from Grok Build itself. Its CLI reference has no command that names the signed-in account, and /session-info shows only the “Auth method (OAuth vs API key…)”. Name each GROK_HOME folder after its account, and choose the account carefully at sign-in.

Enjoy Agentic Industries · Checked against its sources on