v2.3.1

Adds codex-multi-auth history, so you can see all your local Codex sessions.

npm i -g codex-multi-auth

Why this exists

People reported "history isn't shared across accounts". It isn't an account problem — the session files are never split per account. It's a provider filter.

codex resume only shows sessions whose recorded model_provider matches the current one. While rotation or app bind is active, that provider is codex-multi-auth-runtime-proxy, so any session you created under the native openai provider disappears from the list. And vice versa. The files are all still there.

The command

codex-multi-auth history              # every session, newest first
codex-multi-auth history show <id>    # one session's metadata and first messages

Both take --json. Reopen anything with codex resume <id>.

list shows each session's timestamp, provider, id, thread name, and working directory — regardless of which provider recorded it, so nothing is hidden.

It reads the rollout files under <codex-home>/sessions directly (honouring CODEX_HOME). Read-only: no network calls, and it never touches Codex or multi-auth state. Malformed JSONL lines are skipped, and a missing sessions directory is an empty list rather than an error.

Note

The provider filtering lives in the upstream Codex CLI, not here. To get its native view back, run rotation unbind-app or rotation disable. history is the way to see everything without changing your active provider.

---

Closes #612