Bug: Z.ai team coding plan usage data could not be fetched

[zqbake]

Problem

Before PR #1694, Z.ai team-scoped coding plan accounts could not return usage data in CodexBar. Personal scope worked, but team plan accounts did not surface quota or model-usage information.

Impact

• Team plan users saw missing or empty usage data.
• The app could not reflect the active team subscription state.
• This blocked CodexBar for a real Z.ai team workflow.

Expected

When a Z.ai account is configured for team usage, CodexBar should fetch quota and model usage with the team context and display the data normally.

Notes

• Screenshots and additional repro evidence will be added later.
• Related fix: PR Support z.ai BigModel team usage #1694.

[clawsweeper]

ClawSweeper review: did not complete due to Codex infrastructure failure. Reviewed June 23, 2026, 12:36 PM ET / 16:36 UTC.

Summary
Codex review failed: timeout (exit 0).

Reproducibility: unclear. The review failed before ClawSweeper could establish a reproduction path.

Ways to help us reproduce this

• Add a screenshot or short recording showing the behavior.
• Include the exact command, prompt, or workflow that triggered it.
• Add expected vs actual behavior.

Next step
Review did not complete, so no work-lane recommendation was made.

Review details

Best possible solution:

Retry the Codex review after fixing the execution failure.

Do we have a high-confidence way to reproduce the issue?

Unclear. The review failed before ClawSweeper could establish a reproduction path.

Is this the best way to solve the issue?

Unclear. Retry the review first so ClawSweeper can evaluate the actual issue and fix direction.

AGENTS.md: unclear because the file could not be read completely.

Remaining risk / open question:

• No close action taken because the review did not complete.

Codex review notes: model internal, reasoning high; reviewed against f2dede1d9086.

Label changes

Label changes:

• add issue-rating: 🦪 silver shellfish: Current issue advisory state selects this label.
• add clawsweeper:needs-info: Current issue advisory state selects this label.

Evidence reviewed

What I checked:

• failure reason: timeout.
• codex failure detail: Codex review failed for this issue: Codex process timed out after 1200000ms.
• codex stderr: No stderr captured.
• codex stdout: {"type":"thread.started","thread_id":"019ef544-e2d4-7750-ac3f-2f43f492e94a"}.
• process error code: ETIMEDOUT.

Likely related people:

• unknown: Codex failed before it could trace repository history. (role: review did not complete; confidence: low)

How this review workflow works

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.