OpenCode with more than one account per provider

OpenCode 1, the version opencode.ai/install and the opencode-ai npm package give you, doesn't support multiple accounts for one provider. Its ~/.local/share/opencode/auth.json has room for one login per provider, and a second opencode auth login with another OpenAI or GitHub account overwrites the first. Both stay signed in if each account runs with its own XDG_DATA_HOME, since that gives each one an auth.json of its own.

We read OpenCode's docs on 24 October 2026, and its source at the 1.19.4 tag (22 October 2026) where the docs stop. OpenCode 2 handles this differently, and it gets its own section further down.

Where OpenCode keeps your logins: auth.json#

Whatever you connect, with /connect inside OpenCode or opencode auth login in a shell, lands in one file. The providers page says keys added with /connect "are stored in ~/.local/share/opencode/auth.json", and the troubleshooting page describes the same file as "Authentication data like API keys, OAuth tokens". Windows puts it under %USERPROFILE%\.local\share\opencode.

The source shows why a second account can't fit. The file is a JSON object keyed by provider ID (openai, anthropic, github-copilot, opencode-go), written with file mode 0600, and under each key sits a single value: an API key, an OAuth token set, or a token from a well-known login. A second openai account has nowhere to go except over the first.

To see what the file holds, run opencode auth list (opencode auth ls for short). Its first line names the file it read, for example Credentials ~/.local/share/opencode/auth.json, and each provider follows with its type, api or oauth. Keys that come from your shell, such as OPENAI_API_KEY, are listed apart in a second block called Environment.

What opencode auth login does to the account already there#

A login to a provider you already have overwrites its entry. Sign in to ChatGPT Plus as one account and then as a second, and auth.json keeps only the second; getting back to the first takes another login.

opencode auth logout undoes a login. With no argument it asks which provider to drop, and opencode auth logout openai names it directly. The CLI docs say it "Logs you out of a provider by clearing it from the credentials file", and the code does only that: it deletes the entry and writes the file back. OpenCode sends nothing to the provider, so an API key you remove from OpenCode keeps working until you revoke it in that provider's console.

That data folder holds more than logins, which matters for the next step. The troubleshooting page also lists opencode.db ("projects, sessions, and messages"), log/ and snapshot/ there, so moving the data folder moves your history with it.

How to run multiple OpenCode accounts side by side#

global.ts builds OpenCode's folders from the XDG base directory variables. Set XDG_DATA_HOME=~/.local/share-work and OpenCode reads and writes ~/.local/share-work/opencode/auth.json instead, so a second account needs that one variable and nothing else.

1. Give each extra account an alias in ~/.zshrc or ~/.bashrc:

   bash

   alias opencode-work='XDG_DATA_HOME="$HOME/.local/share-work" opencode'
   

2. In a new terminal, opencode-work auth login asks for the provider; sign in with the second account. OpenCode creates the folder itself.

3. opencode-work auth list should now name ~/.local/share-work/opencode/auth.json on its first line, while plain opencode auth list still lists the first account's providers.

4. From here on, opencode is the first account and opencode-work the second. When you lose track of which folders are in use, opencode debug paths prints every one.

PowerShell has no alias that sets a variable. $env:XDG_DATA_HOME = "$HOME\.local\share-work" followed by opencode works for the window you type it in and no other; to keep it, put a function in your PowerShell profile that sets the variable, runs opencode @args and puts the old value back.

Config isn't part of the split. opencode.json, MCP servers and agents stay in ~/.config/opencode, which follows XDG_CONFIG_HOME, so both accounts share them. History is split, because each data folder has its own opencode.db; moving one session across takes opencode export in one profile and opencode import <file> in the other.

The same trick covers a different case: one OpenAI account through a ChatGPT sign-in and another through an API key. Both would go in the openai slot, so they need two data folders as well.

OpenCode 2 keeps several accounts per provider#

OpenCode 2 is a separate install, and the standard script won't give it to you: opencode.ai/install installs OpenCode 1 only, and its comments say OpenCode 2 "ships as @opencode/cli" on npm. The latest version there on 24 October 2026 was 2.1.4.

Its CLI providers page says "Each successful API-key, OAuth, or command login creates a saved account" and "The newest account becomes active". So a second opencode auth login to the same provider adds an account instead of replacing the first. opencode auth list shows them, opencode auth switch makes another one active (named by its label or ID, or picked from a list), and opencode auth logout asks which one to remove. In the TUI, running /connect again on a connected provider opens the same account list. The command came in on 9 September 2026 (switch.ts).

The accounts live in OpenCode 2's SQLite database, not in auth.json. During its database migration it imports the credentials it supports from the old auth.json in its data folder, and new or changed logins are saved in the database, not written back to that file. One account per provider is active at a time, so it's a switch, not two accounts at once.

Is it allowed to use two accounts in OpenCode?#

Use only accounts you own and are entitled to use. Whether a second one is allowed is up to each provider's terms, not OpenCode.

Claude is the clear case. OpenCode's providers page says there are plugins for using Claude Pro or Max in OpenCode, that "Anthropic explicitly prohibits this", and that OpenCode stopped bundling them in 1.3.0. Claude still works in OpenCode with a Claude Console API key, or through Amazon Bedrock or Google Vertex AI. Anthropic's wording, and what it allows instead, are quoted in can you use your Claude plan in OpenCode.

OpenAI is different. OpenCode offers a "ChatGPT Plus/Pro" sign-in under /connect, and OpenAI's own cookbook page on Sign in with ChatGPT, dated 28 September 2026, says its plan-usage integration "is available for open-source tools and personal projects that run locally". That page doesn't name OpenCode, and we didn't check which sign-in route OpenCode uses. OpenAI's Terms of Use still forbid sharing your account credentials, making your account available to anyone else, and circumventing rate limits or restrictions. What they say about holding a second ChatGPT account is in two ChatGPT accounts with Codex: the rules.

How Shuriken runs several OpenCode sources#

In Shuriken, each OpenCode sign-in you add under Settings › Sources is a source (what a source is). Shuriken gives every source a folder of its own under ~/.shuriken/accounts and points XDG_CONFIG_HOME, XDG_DATA_HOME and XDG_STATE_HOME at its config, data and state subfolders: the same isolation as the alias above, with config and state moved too. Adding the source opens a sign-in terminal in the app that runs opencode auth login with those variables, so OpenCode writes that account's auth.json into the source's folder and your own ~/.local/share/opencode/auth.json stays as it was. One source can hold logins for several providers, as one OpenCode install does.

Every OpenCode chat that runs on a source starts with that source's folders. Shuriken reads plan usage for an OpenCode chat in two cases: on an openai/ model with a ChatGPT sign-in it reads that plan's usage the way it does for Codex, and on an opencode-go/ model it reads OpenCode Go's rolling, weekly and monthly windows. For other providers, Shuriken has no usage reading for an OpenCode chat.

OpenCode runs as a chat next to Claude Code, Codex and the other agents, and every chat but a project's Main chat works on its own branch; the OpenCode comparison covers what that adds and what OpenCode's own app already does well. The same folder-per-account approach for the other CLIs is in multiple accounts in every coding agent CLI. Free holds two sources, Pro has no cap, and the download is here.