Before you enrol a Codex account
Codex must keep a ChatGPT login in a file. To check, runpitboard doctor. Its Codex login store line starts with file, and Codex login shows your email address.
pitboard works only with Codex’s default store, the file ~/.codex/auth.json, or $CODEX_HOME/auth.json if you set CODEX_HOME. cli_auth_credentials_store in config.toml, in the same folder, chooses the store. pitboard refuses these values:
keyringandautokeep the login in Codex’s own keychain items. On macOS, every read by another program would ask you for permission.ephemeralkeeps the login in memory only, so there is nothing to park.
/etc/codex/requirements.toml or a project’s own config.
To use the file store, delete the setting or set it to file:
~/.codex/config.toml
codex login and sign in with ChatGPT, so Codex writes its login to the file.
An API-key sign-in has no account login to park. If Codex uses one or is not signed in, run codex login and sign in with ChatGPT.
Add Codex accounts
- App
- Command line
- Click pitboard’s item in the menu bar, then choose Add Account.
- If the dialog shows a Tool pop-up menu, click it and choose Codex. If Codex is not offered, install Codex, then quit pitboard and open it again. The app looks for
codexonly when it opens. - Enter a name such as
work, then click Sign In. Your browser opens. - Sign in with the ChatGPT account you are adding. The dialog closes and the account appears in the Accounts pane.
codex: it still holds the old login.codex login yourself: it revokes the login in use. For why, see Add another account. To rename or forget accounts, see Add and manage accounts.
How Codex accounts differ
- A running
codexnever picks up a switch. Quit it, without typing/logoutin it, and start it again, as What happens to open sessions explains. - pitboard reads the account from the login itself, without asking OpenAI. Two people in one ChatGPT Team or Business workspace are two accounts.
- A switch still asks OpenAI whether it accepts the incoming login, by reading that account’s usage. That read does not count toward your limits.
- A parked Codex login shows
readywith nogood fortime, because Codex states no expiry. - On macOS, pitboard passes a parked Codex login to the keychain command
securityas an argument, and says so after a switch or a--sign-in. See Large logins on macOS.