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?
Keep personal, business, and enterprise Codex profiles signed in at the same time. Masaka gives each authorized identity its own CODEX_HOME, reads official 5-hour and weekly usage windows, and starts the next native Codex process without copying tokens, logging other profiles out, or bypassing quotas. Open source and local-first.
