Claude Code: switch between Team and personal orgs

To switch organization in Claude Code, run /logout, then /login, and pick the other organization in the browser before you approve. Then run /status: its Organization and Email rows say which one you're on now. If you want a Team org and a personal plan signed in at the same time, give each one its own CLAUDE_CONFIG_DIR.

Why Claude Code signs in to the wrong organization#

One email address can belong to two places at once. Anthropic's help article on joining a Team or Enterprise organization lets you keep your personal account when you join with the same address: "Your personal account stays active. You can switch between it and your organization account from your account menu." On claude.ai that menu is your name in the lower left corner, and a blue checkmark marks the account in use.

Claude Code has no such menu. It keeps one claude.ai login per configuration folder, and that login belongs to one organization. Which one you get is decided in the browser when you approve the sign-in.

Anthropic's docs don't describe that browser step for people in two organizations. In a bug report on the claude-code GitHub repo (#12740, November 2025), the reporter had one email on a Pro plan and a Team plan, picked the Team organization in the browser's organization selector, and still ended up on Pro. So treat the browser page as a request and /status as the answer.

Check which organization Claude Code is using#

• Inside a session, run /status. Look at the Login method, Organization and Email rows. When both a login and an API key are configured, /status marks the one that isn't in use.
• Outside a session, run claude auth status --text. Without --text it prints JSON, and it exits with code 0 when you're logged in and 1 when you're not, which is handy in a script.

If the Login method row names an API key, the organization question is the wrong one: an approved ANTHROPIC_API_KEY outranks every claude.ai login. Claude Code using your API key, not your plan covers finding and removing it.

How to switch organization in Claude Code#

1. Run /logout at the Claude Code prompt. Anthropic's authentication page says this also resets your first-launch setup, so the next start walks you through login again.
2. Run claude (or /login) and choose the claude.ai account option, not the Console one.
3. In the browser, if claude.ai asks which organization to connect, pick the one you want, then approve.
4. Back in the terminal, wait for Login successful and press Enter.
5. Run /status and check the Organization row.

From a shell, claude auth logout and claude auth login do the same two steps. claude auth login --email you@example.com pre-fills the address.

If a Remote Control session is running in another terminal when you switch, the error reference says it stops with "signed-in claude.ai account or organization changed on this machine", because it belongs to the login it was started under. The local session keeps going; run /remote-control there to start a new one on the current organization.

Make the login pre-select the right organization#

When the browser keeps handing you the wrong organization, let Claude Code ask for the right one. The settings reference says a single organization ID in forceLoginOrgUUID in any settings file "pre-selects the organization during login without restricting it". Only managed settings enforce it.

{
  "forceLoginOrgUUID": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
}

Put it in ~/.claude/settings.json, or in the settings.json of the profile folder described below. A Team or Enterprise organization's ID is shown in claude.ai's admin settings. For an organization you're already signed in to, Claude Code writes the ID into .claude.json as organizationUuid under oauthAccount. Shuriken reads that same field, but Anthropic doesn't document it, so it may move.

One side effect from the same page: with forceLoginOrgUUID in any settings file, Claude Code stops offering the keyless Console sign-in and creates an API key for Console logins instead.

Use a Team seat and a personal plan at the same time#

Logging out and in works for an occasional switch. If you move between work and personal code every day, keep both logins. Anthropic's answer is one configuration folder per account:

alias claude-work='CLAUDE_CONFIG_DIR=~/.claude-work claude'

claude keeps your personal login in ~/.claude, and claude-work signs in to the Team organization in its own folder the first time you run it. Each folder has its own settings, session history and claude.ai login, and on a Mac its own Keychain entry. Add the forceLoginOrgUUID line to ~/.claude-work/settings.json and the work profile asks for the right organization every time it signs in.

The price is that nothing is shared: claude --resume in one profile doesn't list the other profile's sessions, and user-level MCP servers and settings are set up twice. Two Claude Code profiles with CLAUDE_CONFIG_DIR lists what each folder keeps to itself and how to share the parts you want shared.

forceLoginOrgUUID errors and blocked API keys on a work machine#

If your company manages your laptop, the same key can be set in managed settings, often next to forceLoginMethod. Then it stops being a hint. Per the authentication docs:

• A claude.ai login to any organization that isn't listed gets an error, and Claude Code exits at startup if the login in use belongs to one that isn't listed.
• First-launch setup shows the login prompt even after an earlier sign-in, whether or not your account belongs to a listed organization. Log in with an account in one of them to get past it.
• ANTHROPIC_API_KEY, ANTHROPIC_AUTH_TOKEN and apiKeyHelper are blocked at startup, because organization membership can't be checked for them.
• forceLoginMethod set to "claudeai" or "console" names the kind of account the machine expects. The terminal's own login screen only pre-selects it, but an earlier sign-in of the other kind no longer counts, so the login prompt comes back.

A different message, "Your organization has disabled Claude subscription access for Claude Code", is a setting on the organization's side. The error reference says local settings, environment variables and flags can't override it. An admin can turn access on; until then, the page's other way out is a Console API key.

These are your employer's rules for that machine. If your personal plan can't sign in there, that is the policy working. Use your personal plan on your own computer, or ask the admin.

Team terms and personal terms are different#

Which organization you're signed in to decides more than whose limits you use. Anthropic's legal and compliance page puts Claude Code on Team and Enterprise under the Commercial Terms, and on Free, Pro and Max under the Consumer Terms. Company code that runs on your personal login is under the consumer terms; your personal Claude account for work code goes through what that changes.

Don't fix a same-email muddle by merging the accounts unless you mean it. The help article's "Use your organization account only" option closes your personal account and cancels an active Pro or Max subscription (one bought through the App Store you cancel yourself), and moving your chats into the organization is one-way.

The limits differ too. A Team seat has its own 5-hour and weekly limits, set by seat type rather than by your personal plan; Claude Team seats for Claude Code has the numbers and prices.

How Shuriken handles a Team seat and a personal plan#

In Shuriken each Claude sign-in you add is a source, and Shuriken tells Claude sources apart by email address. If your Team seat is on your work address and your Pro or Max plan on a personal one, add both in Settings › Sources with Add source, choosing Sign in for each. Then tag them: click the Tags column on each row and create Work and Personal. A Team seat also shows its 5-hour and weekly limits like any other source.

If both organizations share one email, Shuriken sees the second sign-in as the same account: it says the source "was already here" and signs it in again with the new login. You end up with one source, on whichever organization you approved last. For now, a Team seat and a personal plan need different addresses to be two sources in Shuriken.

Tags don't steer chats. With Automatic on (Sources › Switch settings), switching moves chats to another source when the one in use reaches your switch point, 99% by default, and that includes moving work chats onto your personal plan. The Use button on a source picks it for every chat on every device, and with Automatic off they stay there. The choice is one per agent, not per project. If company code must stay on the company seat, turn Automatic off, or keep the personal plan out of that Shuriken account.

Add only accounts you own and are entitled to use, and check what your employer allows on each.