I've become a bit addicted to Codex recently. Then I quickly encountered my first real pain point: one account was simply not enough. It’s not that I don’t have enough capabilities, or that there aren’t enough terminals, but that I naturally started to want to separate different tasks and run them in parallel. Use one window to write code, another window to continue changing the architecture, one account to focus on the current project, and another account to open a new thread for exploration. I now basically run 8-9 parallel tasks at the same time. It was quickly discovered that as long as two accounts share a local login status and browser identity, the one logged in later will override the previous one. Later I realized that this was not "the Codex cannot be opened multiple times", but "the login state is not isolated". The solution is actually very engineering:
- Assign a separate set of CODEX_HOME to each account, such as codex-a and codex-b, and then use different browser profiles to authorize them. 2 I configured open-chrome-a and open-chrome-b for myself. First open the corresponding Chrome profile, and then execute codex-a login --device-auth and codex-b login --device-auth respectively. In this way, browser cookies, local credentials, cache, and history will be completely separated, and the two accounts can be truly stable and parallel. Once you start using Codex frequently, many questions are no longer "can it be used?" but "how to turn it into a sustainable workflow." Similar operations are required for more than two accounts. Tips: - CODEX_HOME must be separated - Chrome Profile must also be separated - Half of the window: open-chrome-a -> codex-a login --device-auth - The other half of the window: open-chrome-b -> codex-b login --device-auth - After the first authorization is completed, it is enough to run codex-a / codex-b directly in the future.