Several accounts and computers, one task list

The manual way

# two logins, one folder each
claude                                        # your usual account
CLAUDE_CONFIG_DIR=~/.claude-work claude       # the other one

# and on each computer, its own terminals
ssh desktop    # tmux, worktrees, which account was this?
ssh devbox

It works, until you have a terminal per account per computer and per project. Nothing tells you which session runs on which plan, which one is waiting for an answer, or which one is done.

With wisp

1. Start wisp.
   npxnpmcurlbrewDownload

   $npx wisp-agentsCopy

   macOS · Linux and Windows in beta · Node 20+ · MIT

2. Add the second account. Settings → Agents → Add another Claude account (or Codex), as personal or work. It signs in with the CLI’s own sign-in into a folder of its own; settings, skills, MCP servers and transcripts are shared with your first account, the login never is. See work and personal accounts.
3. Add your other computers. Machines → Reach this computer from anywhere on each one (no SSH, through wisp Cloud), or connect over SSH or Tailscale. See agents on several machines.
4. Pick per task. In the launcher, Run on says which computer (or several at once), and the runner picker’s Account row says which account. A machine has its own accounts, so the row lists what’s signed in there.
5. Read one list. Tasks from every computer and account join the same list, with the machine on the card. Questions from any of them come to Needs you, and to your phone with ntfy or Telegram.

Too many projects

• Every project runs on every computer. A machine without a checkout gets one first: wisp reuses a clone of the same repo it finds there, or clones the project’s origin.
• One task, several folders. ⌘/Ctrl-click another project in the launcher and the agent works in both, with a worktree per repo. Ship it opens a PR per repo with changes.
• Move a task. Runs on next to the reply box moves your next follow-up and the task to another computer, with its branch and uncommitted work. See move a task.

Limits stay per account

Each account keeps its own 5-hour and weekly windows, and wisp doesn’t pool them. When one runs out, the task asks you: wait for the reset, continue on another of your accounts, hand it to another agent, or get extra usage. wisp never switches accounts on its own. Settings → Usage → Plan budget shows how much of each account’s windows is gone and which tasks used it; see where your usage went.