How do you keep multiple Codex workspaces signed in?

by•

I built Masaka after Personal, Business, and Enterprise Codex identities kept colliding in one CODEX_HOME. Each authorized account/workspace pair owns isolated state, while the official Codex login still owns authentication. Direct mode selects the next native Codex process; optional proxy mode can switch the next request only after any in-flight response finishes. It does not copy tokens or bypass quotas.

How are you handling this today—repeated logout/login, separate OS users or containers, one account per machine, or something else?

The project is open source:

What switching or usage-visibility failure should the next release cover?

1 view

Add a comment

Replies

Be the first to reply

Have a question or a thought to share? Add a comment above to start the conversation.