01
duoterm add <name>create an account slot
once
—
02
duoterm login <name>sign it in, in the browser
once
—
03
duoterm use <name>switch. No sign-out
daily
—
04
duoterm listaccounts and emails, current starred
daily
—
05
duoterm run <name> [args]one session as another account
ad hoc
—
06
duoterm with <name> <cmd>any command, that environment
ad hoc
—
07
duoterm syncrelink shared config
as needed
—
08
duoterm doctorcheck the wiring
as needed
—
09
duoterm remove <name>delete a slot, never the primary
rare
—
Every slot links CLAUDE.md, settings, commands, hooks, skills, agents, plugins and projects back to your primary. Identity is the only thing that differs, and the credential never leaves its own keychain item.
- slots
- unlimited
- switch
- local
- state
- one word
- deps
- none
Not shared, on purpose: .claude.json and the credential itself. That is the whole of what makes one slot a different account from another.
$duoterm liststarred = live
Add your own entries to the shared list in shared.conf and run duoterm sync. Anything you place in a slot by hand is left alone, so a per-account override stays an override.
$duoterm doctordangling links, missing logins