Launching today

Masaka for Codex

Launching today

Switch isolated Codex accounts and workspaces

0 followers

Switch isolated Codex accounts and workspaces

0 followers

Visit website

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.

Free

Launch tags:Productivity•Developer Tools•Artificial Intelligence

Launch Team

ClarifyThe full-stack AI CRM for modern GTM teams

Promoted

Maker

📌

I built Masaka for a specific failure mode: switching among personal, business, and enterprise Codex identities without signing another profile out. Each authorized login keeps its own CODEX_HOME; Masaka reads official 5-hour and weekly usage windows and starts the next native Codex process. It never copies tokens or bypasses quotas. I’d value feedback from people already juggling multiple Codex workspaces: what switching or usage-visibility problem is still missing?

Report

17h ago

Forum Threads

p/masaka-for-codex

•

16h ago

How do you keep multiple Codex workspaces signed in?

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?

View all