Open Source · MIT · Pure bash · v0.6.2
clikae
**Your starting point for AI coding CLIs — and the cost-aware control plane for a fleet of them.**
Two Claude accounts because one ran dry, a Codex login, maybe Antigravity too — in different terminals, half of them unfinished. Type clikae and land on your recent sessions, newest first, each with a one-line recap of where you left off. Pick one, hit Enter, and you're back exactly where you were.
How it works
1.
Make a tank
A tank is one account or config, kept in its own isolated directory so logins never collide. clikae init claude work creates one; clikae claude work opens it and you log in once.
2.
Work as usual
Run your sessions through clikae across as many accounts and engines as you like. It reads each session's own recap for free — nothing is sent anywhere — so the board can show where you left off.
3.
Land on the board
Type clikae to land on your recent sessions, newest first, above your tanks in a single burn order. Pick a session and resume it, or pick a tank and start fresh — right account, right session.
What's inside
Cross-account, cross-engine
One board shows every account and every engine — Claude Code, Codex, Antigravity — not just the one you're logged into right now.
Recaps, read for free
Each session carries a one-line recap of where you left off, read from the session's own summary. No extra model calls, no network, no cost.
A fuel-gauge board
Your tanks are one reorderable burn order, each with a traffic-light dot: green ready, red dry (with its reset time), or blank when it can't be read. See which account still has quota at a glance.
Carry a session onward
Hit a limit mid-task? clikae to <tank> keeps the same conversation going on another account's quota; clikae to <engine> hands a written brief across vendors, summarized on-device by a local model when you have one.
Route work to a live tank
clikae burn runs a headless task on a tank and verifies it by the file it should produce — never the exit code — then re-fires the same task on your next tank when one runs dry. Send the grunt work to whichever account still has quota.
Cost-aware, never your main budget
This is the point: every account burns its own subscription quota, so fanning work out never eats the budget you're using for your main session. clikae knows which tank is live and which logins share a limit, so burn skips them — the expensive supervisor stays asleep while cheap workers burn whichever account still has gas. No proxy, no daemon, no traffic interception — it reshapes where your state lives, never sits in the middle of your requests.
Fan a job across accounts (BETA)
clikae conduct runs one prompt headless across several accounts in parallel — each on its own quota — and collects every result for you to compare. clikae git-id pins each tank's commit identity so dispatched work never commits as the wrong account. It's built as much for an LLM driving clikae as for a person.
Your connectors ride along
A tank isolates the claude.ai login, so the MCP connectors set up on that account come with it — switch tank and the Stripe, Drive, or WordPress tools live in your session switch too. clikae doesn't manage MCP; this is per-account isolation paying off.
Try it
brew install CVERInc/clikae/clikae, make a tank or two, then type clikae. One person, a fleet of AI coding CLIs, each on its own quota. Pure bash — every line is auditable — with no daemon, no global state, and exactly one opt-out network call. macOS and Linux, MIT. It's a tool for agents as much as people: the fastest way to wield the fleet is to point your Claude at the orchestration playbook and let it drive — the full guide is in the README.