If you take on client work with Claude Code and Codex, you already know the specific annoyance this article is about.
Client A's account is authenticated in your terminal. You're mid-session, everything's flowing.
Then Client B pings you with something urgent, and now you have to log out of Client A, run through the login flow again for Client B, wait for the browser auth to confirm, and only then get back to actually fixing the thing.
At one point I was running three separate Claude Code accounts for three different clients, plus two Codex accounts, one for a contract and one I kept for testing side projects. Five accounts, one terminal, constant logins.
Do that four or five times a day across a handful of clients and it stops being a minor inconvenience.
It becomes a tax on every context switch, on top of the mental tax of remembering what you were doing before you got interrupted.
The account problem is annoying. The engine problem is separate and just as real
There's a second, less talked about version of this friction. Claude Code and Codex aren't the only serious options anymore.
Tools like OpenCode, Copilot, and Qwen Code all have real strengths depending on the task, the model underneath, or just what you're in the mood to experiment with.
But trying a different engine mid-project usually means a separate install, separate configuration, and often a completely different terminal workflow to learn on the spot.
So most people just don't bother, and stick with whatever they set up first, even when a different engine would genuinely be a better fit.
How Clopen handles multi-account without the logout dance
In Clopen, you add your accounts once, in the UI, and from there switching is a selection in project settings rather than a terminal command.
Each project can be pinned to a specific account, so opening Client A's project just opens it with Client A's credentials already active, and Client B's project does the same with theirs.
You're not checking which account is logged in before you start working. You just open the project.
This matters more than it sounds like on paper. The logout-login cycle isn't just slow, it's a full context reset.
You leave your terminal, deal with an unrelated authentication flow, and come back having to reload the mental state you were in.
Making the switch a single click removes the reset entirely. You're never "logging in," you're just choosing which project to work in, and the account comes with it.
Real engines, real SDKs, not a router trick
The part worth explaining a bit more technically: Clopen doesn't put a proxy or a unified router in front of these tools to fake compatibility.
It integrates with the official SDKs of each engine directly, Claude Code's own SDK, Codex's own SDK, OpenCode's own SDK, and so on.
That distinction matters because a routing layer tends to lag behind upstream changes, silently breaks when an API shifts, and often can't fully expose engine-specific behavior.
Talking to each engine through its own SDK means you get the actual capabilities of that engine, not a lowest-common-denominator abstraction sitting between you and it.
Practically, this means picking OpenCode for a project because you want to try a different model behind it, or because its output style fits a particular kind of refactor better, is a dropdown choice in that project's settings.
No separate install, no new config file to hand-write, no learning a second CLI's flags from scratch.
You pick the engine, the session starts on it, and you can switch back just as easily next session.
Why this is worth solving properly
None of this is the interesting part of the job. Nobody bills a client for the fifteen minutes spent re-authenticating.
But that time, and more importantly, the mental context it costs, comes directly out of the hours you actually want to spend building.
Multi-account and multi-engine support isn't a headline feature you'd put on a landing page hero image. But it's exactly the kind of friction that determines whether a tool feels professional-grade or feels like a demo.
Get your accounts and engines out of your way
If you're juggling clients, or just want to try a different engine without a fresh setup every time, this is a solved problem in Clopen.
bun add -g @myrialabs/clopen
Add your accounts once, assign them per project, and pick your engine per session. Check out the GitHub repository, the landing page, and if you end up wanting a specific engine we don't support yet, that's exactly the kind of contribution the project could use.
Top comments (0)