[BUG] TUI renders phantom quota 100% for disabled zero-minute secondary window

[aic0d3r]

Bug Description

The OpenCode TUI status renders a phantom quota 100% segment when OpenAI returns a disabled secondary quota window with window-minutes: 0 and used-percent: 0.

The real primary weekly value is displayed correctly, but the disabled secondary window is also included and formatted as a generic quota limit.

Example status:

7d 77% · quota 100%

Steps to Reproduce

1. Use a paid Team workspace whose Codex response headers include a weekly primary window and a disabled secondary window:

x-codex-primary-used-percent: 23
x-codex-primary-window-minutes: 10080
x-codex-secondary-used-percent: 0
x-codex-secondary-window-minutes: 0
x-codex-secondary-reset-at:
x-codex-secondary-reset-after-seconds: 0

2. Send a successful Codex request through the plugin.
3. Observe the OpenCode TUI status line.
4. Inspect ~/.local/state/opencode/oc-codex-multi-auth-tui-quota.json.

The generated cache includes:

{
  "label": "quota",
  "leftPercent": 100,
  "usedPercent": 0,
  "windowMinutes": 0
}

Deleting the cache does not resolve the issue; the clean v6.7.1 runtime recreates the same entry from subsequent response headers.

Expected Behavior

A secondary window explicitly reported with window-minutes: 0 should be treated as disabled and omitted from the TUI quota display. Only the real weekly limit should appear:

7d 77%

Actual Behavior

The TUI displays:

7d 77% · quota 100%

Environment

• opencode version: 1.17.19
• Plugin version: 6.7.1 (clean install; no local patches loaded)
• Operating System: Linux
• Node.js version: v24.3.0
• Plan: paid Team

Possible Cause

In lib/tui-quota-cache.ts, parseLimit() formats a non-positive/absent window as quota. hasUsefulLimit() then retains it because usedPercent is numeric even when windowMinutes === 0:

return Boolean(
  limit.windowMinutes ||
  typeof limit.usedPercent === "number" ||
  typeof limit.resetAtMs === "number"
)

A narrow fix may be to reject a limit when windowMinutes === 0, while preserving generic limits where the window header is genuinely absent.

Logs

No raw request logs attached because they contain unrelated response metadata. The relevant sanitized x-codex-* fields are included above.

Compliance Checklist

• I'm using this plugin for personal development only
• I have an active paid ChatGPT Team subscription (Team equivalent; template says Plus/Pro)
• This issue is not related to attempting commercial use or TOS violations
• I've reviewed the FAQ and Troubleshooting sections

Additional Context

The server usage endpoint reports the real weekly allowance correctly. This issue is limited to parsing/rendering the disabled secondary header window in the TUI status cache.

[coderabbitai]

🔗 Related PRs

#70 - feat(codex-limits): add codex-limits tool and deduplicate accounts by refreshToken [closed]
#146 - [codex] add OpenCode TUI prompt status [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[aic0d3r]

Additional context: this appears correlated with OpenAI temporarily disabling the 5-hour Codex limit for some paid plans.

A public report from Jul 12 says the 5-hour limit was temporarily removed and usage became weekly-only:
https://x.com/andr3barroso/status/2076402303263969444

OpenAI's current response shape on the affected Team workspace is consistent with that change: the weekly window remains active, while the secondary window is still present in headers but encoded as disabled (window-minutes: 0, used-percent: 0, empty/no reset).

The temporary policy change is likely the trigger, but the plugin-side issue remains: a zero-minute disabled window should be omitted instead of rendered as quota 100%.