wisp GitHub

Guide

Use your work and personal Claude Code accounts

Claude Code keeps its login in one folder, and CLAUDE_CONFIG_DIR points it at another, so a second account is a second folder. wisp sets that up for you: add the account in Settings → Agents, pick it per task, and when one reaches its limit the task asks you what to do.

Source on GitHub

Free and open source · Claude Code, Codex, Cursor CLI, opencode, Antigravity CLI, Grok Build, Copilot CLI · macOS, Linux, Windows (beta) · Node 20+

A wisp task whose Work account reached its usage limit: Wait until the reset, Continue on Personal, Hand to Codex or Get extra usage

The manual way

# a second login in a folder of its own
CLAUDE_CONFIG_DIR=~/.claude-personal claude auth login

# then run each session on the account you mean
claude                                        # your usual account
CLAUDE_CONFIG_DIR=~/.claude-personal claude   # the other one

Codex works the same way with CODEX_HOME. Things to know: the second folder starts empty, so your settings, skills, MCP servers and past sessions aren’t there, and you have to remember which shell runs which account.

With wisp

  1. Start wisp.
  2. Add the account. Settings → Agents → Add another Claude account (or Codex). Name it, say whether it’s personal or work, and sign in with the CLI’s own sign-in: a link and a code, no terminal. wisp never sees your password.
  3. Everything but the login is shared. The new account’s folder (~/.wisp/accounts/claude/<id>) links to your usual one for settings, skills, MCP servers and transcripts. The login stays separate.
  4. Pick the account per task. The runner picker has an Account row under Thinking, and the reply box can switch a task to the other account from its next follow-up. wisp remembers your pick per harness, and the task’s details say which account ran it.

When an account reaches its limit

Each account keeps its own usage limits, and wisp doesn’t combine them. When one runs out, the task stops and asks: wait until the reset (wisp sends the follow-up then), continue on another of your accounts in the same conversation, hand the task to another agent like Codex, or get extra usage from the provider. Moving a conversation between a work and a personal account says so first, since its code goes with it.

wisp never switches accounts on its own, and tasks that run without you (crew members, schedules, subagents) stay on the account you picked.

Which accounts to add

Only accounts that are yours: your own plan, or a seat your employer gave you. Sharing a login with someone else is against Anthropic’s and OpenAI’s terms and can get the account closed. Before you use a work account on personal projects, or the other way round, check your employer’s rules. For heavy automated use, the providers ask you to use an API key, which wisp supports too.

Questions

Which agents can have more than one account?
Claude Code and Codex, the two whose login lives in one folder you can point elsewhere (CLAUDE_CONFIG_DIR, CODEX_HOME).
Does wisp switch to my other account when I hit a limit?
No. The task asks you: wait for the reset, continue on another of your accounts, hand it to another agent, or get extra usage from the provider.
Does the second account see my MCP servers and skills?
Yes. Its folder links to your usual one for everything except the login, and its settings file copies your MCP servers without who is signed in.
Can my team share one Claude account through wisp?
No. Each person signs in with their own account; Anthropic’s and OpenAI’s terms don’t allow sharing a login.