Two accounts of the same CLI, side by side

• Work and personal. A Team or Enterprise seat for the day job and a personal Max or Pro plan for your own projects, both Claude Code, both on the same Mac.
• Client separation. Consultants who bill usage per client keep one account per client and need them side by side, not switched.
• Two ChatGPT accounts. The same applies to Codex. Profiles exist today for Claude Code and Codex, the two CLIs that have their own setting for moving their sign-in folder. For other CLIs, see the manual route below.

Logging out and back in works, and destroys the flow: the sessions you were in are tied to the account, the browser round trip takes a minute, and you do it several times a day.

Claude Code and Codex can each have several profiles in Symvibe. Each profile gets its own configuration folder, set through the CLI's own setting for it (CLAUDE_CONFIG_DIR or CODEX_HOME), so the CLI sees its own configuration, its own login and its own session history, and never the other profile's. When you spawn a console you pick the profile, and two consoles of the same CLI under different profiles run side by side on the same board.

You can start a profile empty and sign in inside it, or save your current sign-in as a profile, which copies that CLI's sign-in files into the profile's folder on your Mac. Nothing is uploaded. One limit on macOS: Claude Code can keep its sign-in in the system Keychain, which a profile cannot fully separate, so after switching check the account with /status in the console.

• Sessions and resume stay per profile. A console relaunched on reopen resumes the conversation of the account it belongs to.
• Same repo, two accounts. Both consoles can point at the same repository. If both write, put each one in its own git worktree, exactly as with any two parallel agents.
• No pooling, no rotation. A console is signed in as one of your accounts and stays that way. Symvibe does not merge limits, switch accounts behind your back or share credentials between consoles.

The same idea works without Symvibe, with a little shell work per CLI.

Claude Code

Claude Code reads CLAUDE_CONFIG_DIR to move its configuration and session storage off ~/.claude. Give each account its own directory and start the CLI with the variable set:

CLAUDE_CONFIG_DIR=~/.claude-work claude -n api-cleanup
CLAUDE_CONFIG_DIR=~/.claude-personal claude -n side-project

Two shell aliases make it permanent. Sessions started under one directory resume under that same directory.

Any CLI

For a CLI without a setting of its own, the general trick is a separate HOME:

HOME=~/homes/work codex
HOME=~/homes/personal gemini

Two caveats. A different HOME also changes where the shell finds its own configuration, your git identity and anything else that lives in the home directory, so set up those files in the new home too. And on macOS some CLIs keep the login in the system Keychain rather than in the home directory; test it once, by signing in under the second home and confirming the first is still signed in.