Display Name
clikae
Category
Tooling
Sub-Category
Tooling: Orchestrators
Primary Link
https://github.com/CVERInc/clikae
Author Name
CVER Inc.
Author Link
https://github.com/CVERInc
License
MIT
Other License
No response
Description
Points an AI coding CLI at one of several isolated per-account configurations and runs it, so multiple Claude Code, Codex, and Antigravity logins coexist without clobbering each other. A home board lists recent sessions newest-first with a one-line recap and a fuel indicator showing which account still has quota, and a live session can be carried onto another account or handed across vendors as a brief summarized on-device.
Validate Claims
Create two tanks for Claude Code, start a session on one, then run "clikae to " and confirm the same conversation resumes on the second account via --resume.
Specific Task(s)
Resume an in-progress Claude Code session onto a second account after the first hits its usage limit.
Specific Prompt(s)
Run "clikae" to open the home board, pick the in-progress session, then "clikae to personal" to carry it onward and continue the task.
Additional Comments
I built clikae to scratch my own itch. I kept hitting the Claude Max 20x usage limit mid-task, and moving to another account meant losing all my context and hand-writing a handoff I never had time for. clikae lets me carry the same live session — memory and all — onto another account the moment one runs dry, so the work just continues and the project stays safe. I've been dogfooding it daily, and I'm recommending it in case other people juggling multiple accounts keep hitting the same wall.
Recommendation Checklist
Display Name
clikae
Category
Tooling
Sub-Category
Tooling: Orchestrators
Primary Link
https://github.com/CVERInc/clikae
Author Name
CVER Inc.
Author Link
https://github.com/CVERInc
License
MIT
Other License
No response
Description
Points an AI coding CLI at one of several isolated per-account configurations and runs it, so multiple Claude Code, Codex, and Antigravity logins coexist without clobbering each other. A home board lists recent sessions newest-first with a one-line recap and a fuel indicator showing which account still has quota, and a live session can be carried onto another account or handed across vendors as a brief summarized on-device.
Validate Claims
Create two tanks for Claude Code, start a session on one, then run "clikae to " and confirm the same conversation resumes on the second account via --resume.
Specific Task(s)
Resume an in-progress Claude Code session onto a second account after the first hits its usage limit.
Specific Prompt(s)
Run "clikae" to open the home board, pick the in-progress session, then "clikae to personal" to carry it onward and continue the task.
Additional Comments
I built clikae to scratch my own itch. I kept hitting the Claude Max 20x usage limit mid-task, and moving to another account meant losing all my context and hand-writing a handoff I never had time for. clikae lets me carry the same live session — memory and all — onto another account the moment one runs dry, so the work just continues and the project stays safe. I've been dogfooding it daily, and I'm recommending it in case other people juggling multiple accounts keep hitting the same wall.
Recommendation Checklist