Token conflict. Run codex to log in again.

[Srini-B]

I did it, did it on codex terminal and also on chatgt, Started happening after i installed codex app

[davidarny]

Hey @Srini-B !

Would appreciate if you take time and follow this instruction to get some logs. Would be very helpful!

[Srini-B]

uninstalled the codex app, updated codex cli, logged out of it, logged in -
OpenUsage.log

[davidarny]

@Srini-B thanks a lot! Will take a look soon.

[davidarny]

Thanks for the logs — this looks deeper than a simple restart/relogin.

Your OpenUsage log shows:

• OpenUsage reads Codex auth from macOS keychain (Codex Auth)
• refresh call fails with 401 / refresh_token_reused

When both Codex Desktop + Codex CLI are used, this can happen if a stale keychain entry is still being picked after token rotation.

Please try this exact reset on macOS:

1. Quit OpenUsage + Codex Desktop + all codex terminal sessions.
2. Remove all Codex Auth keychain entries:

   while security delete-generic-password -s "Codex Auth" >/dev/null 2>&1; do :; done

3. (Optional but recommended) move stale auth files out of the way:

   [ -f ~/.codex/auth.json ] && mv ~/.codex/auth.json ~/.codex/auth.json.bak.$(date +%s)
   [ -f ~/.config/codex/auth.json ] && mv ~/.config/codex/auth.json ~/.config/codex/auth.json.bak.$(date +%s)

4. Re-auth once from CLI:

   codex login

5. Open OpenUsage again.

Why this helps: relogin alone may leave an old keychain item in place, and OpenUsage can keep reading that stale refresh token.

If it still fails, please share:

• output of security find-generic-password -s "Codex Auth"
• newest OpenUsage.log lines around [plugin:codex]

I’ll also push a hardening fix so this multi-entry keychain case is handled more safely.