multi-clawd
One Claude is never enough
An OpenClaw plugin that registers your extra Claude Code logins as first-class CLI backends. When your main account hits a usage limit, failover rolls to your second account on the same model — instead of dropping to a smaller one — with every tool, skill, and MCP bridge intact.

Features
What it does.
First-Class Backends
Every account registers as a real CLI backend (claw2/…, claw3/…) — resolvable in model refs, fallback chains, and per-agent overrides. No API keys, no baseUrl hacks.
Same-Model Failover
Exhaust the account, not the model. A usage limit rolls to your next login on the same model — tier drops become the last resort instead of the default.
Full Harness on Every Hop
Each backend is a genuine Claude Code subprocess: native tools, skills, the OpenClaw MCP bridge, and native compaction all survive the hop across accounts.
Token Hygiene
Setup-tokens are read at launch and passed only through the child process environment. Never committed, never logged, never in your config in plain sight.
Self-Healing Registration
If the plugin loader hands over an empty config block, registration re-reads the resolved runtime config directly — a flaky pass can't silently disable your failover.
Isolated Logins
Each account lives in its own CLAUDE_CONFIG_DIR with its own token file, keeping sessions, settings, and auth cleanly separated per login.
How it works
4 simple steps.
Install the Plugin
Clone from GitHub, npm install and build, then openclaw plugins install. One TypeScript plugin, MIT licensed. ClawHub install is landing shortly.
Capture the Second Login
Give the account an isolated config dir and capture its Claude Code setup-token into it — one claude setup-token command per account.
Configure Accounts
List each account in the plugin config. Every account becomes a provider prefix like claw2/ with the full Claude model catalog behind it.
Slot Into the Chain
Add claw2/… to your fallback chain and restart the gateway. Limits now roll across your accounts before any model-tier drop.
One chain, all your capacity
Your fallback chain stops meaning “smaller model” and starts meaning “next account”.
"agents": { "defaults": { "model": {
"primary": "claude-cli/claude-fable-5", // main login
"fallbacks": [
"claw2/claude-fable-5", // 2nd login — same model
"claw3/claude-fable-5", // 3rd login? go on then
"anthropic/claude-opus-4-8" // only NOW drop a tier
]
} } }4
Claws
0
API keys required
100%
Harness intact
MIT
Licence
Frequently Asked Questions
What is multi-clawd?+
Why does this need a plugin at all?+
Does failover keep my skills and MCP tools?+
Is this within my provider's terms?+
How many accounts can I add?+
What does it cost?+
Grow an extra claw
Stop letting your second Claude account sit idle. Install multi-clawd and make your failover chain pool the capacity you already pay for.