Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

The status card shows the correct active OAuth profile for ChatGPT Codex, but the weekly usage line reports 0% left even though that limit appears to belong to a different credential.

Steps to reproduce

1. Configure multiple openai-codex OAuth profiles in OpenClaw.
2. Use OpenClaw with openai-codex/gpt-5.4.
3. Open the status/session status view after the active auth profile is shown as the correct default profile.
4. Observe that the usage line reports a different weekly percentage than the codex cli reports

Expected behavior

The usage/quota line should reflect the usage for the account credential currently set in the session.

Actual behavior

The usage/quota line reflects the usage for the default model, not the fallback model actually being used in the session.

OpenClaw version

2026.3.28

Operating system

macOS 26.3.1

Install method

npm global

Model

openai-codex/gpt-5.4

Provider / routing chain

openclaw -> openai-codex (oauth)

Additional provider/model setup details

Two openai-codex OAuth profiles are configured:

• openai-codex:default — display name ChatGPT Codex - Peter
• openai-codex:k###########@gmail.com — display name ChatGPT Codex - Kate

Logs, screenshots, and evidence

Observed status output:


🦞 OpenClaw 2026.3.28 (f9b1079)
🧠 Model: openai-codex/gpt-5.4 · 🔑 oauth (openai-codex:k###########@gmail.com (ChatGPT Codex - Kate))
🧮 Tokens: 37k in / 220 out
📚 Context: 37k/272k (14%) · 🧹 Compactions: 0
📊 Usage: 5h 100% left ⏱4h 59m · Week 0% left ⏱2d 8h
🧵 Session: agent:main:main • updated just now
⚙️ Runtime: direct · Think: off
🪢 Queue: collect (depth 0)

Impact and severity

Impact and severity

Affected: OpenClaw instances using multiple `openai-codex` OAuth profiles
Severity: Medium
Frequency: Observed in the captured status output
Consequence: The usage/quota line may be misleading when the active auth profile and the reported usage appear to refer to different credentials

### Additional information

not known if this worked in the prior version