Qwen Cloud Individual: monthly usage fails to parse

[IlyaZadyabin]

Qwen Cloud Individual: monthly usage fails to parse

Qwen Cloud does not work in CodexBar 0.65.0 on macOS: it cannot display usage for my Individual Standard plan. Login succeeds, but reading the usage data fails.

Reproduce: Configure Qwen Cloud with a valid cookie, then refresh usage.

Error:

Failed to parse Qwen Cloud usage: Missing token plan data (topKeys=code,data,httpStatusCode,requestId,successResponse dataKeys=DataV2,api,errorCode,errorMsg,httpStatus,success)

The authenticated API returns monthly fields instead of the expected five-hour/weekly fields. Selected fields (nesting omitted):

{
  "per1MonthPercentage": 8.690073333333334e-7,
  "per1MonthResetTime": 1790611200000
}

Expected: Show monthly usage and reset time when these fields are present.

Related: #3711 covers Team plans; this account is Individual. #2328 covers Personal/Solo API support.

[clawsweeper]

Codex review: this still needs some work. Reviewed September 23, 2026, 6:26 AM ET / 10:26 UTC.

Summary
The monthly-only parsing failure remains on main and in v0.65.0. An open PR already changes the shared parser used by Qwen Cloud, so this issue should remain open for Qwen-specific verification of that candidate.

Reproducibility: yes. source establishes that a monthly-only payload cannot pass the current personal parser and falls into the reported legacy error path. No live account probe or test execution was performed; the reporter omitted the complete envelope.

Next step
Review #3903 for Qwen-specific parser and monthly display coverage before resolving this issue; its shared repair makes a second fix PR unnecessary.

Review details

Best possible solution:

Recognize monthly Individual usage through the shared parser, preserve existing windows and provider identity, and display the actual monthly period and reset without requiring cookie reconfiguration.

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

Yes, source establishes that a monthly-only payload cannot pass the current personal parser and falls into the reported legacy error path. No live account probe or test execution was performed; the reporter omitted the complete envelope.

Is this the best way to solve the issue?

Yes, extending the shared parser is the narrowest repair, and the open candidate already takes that path; Qwen-specific regression coverage and monthly display verification should accompany it.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning medium; reviewed against 8a146258a26d.

Label changes

Label changes:

• add P2: A source-supported parsing defect prevents usage display for one supported provider's monthly Individual plans.
• add impact:auth-provider: Authenticated Qwen Cloud Individual accounts cannot obtain a usable provider usage snapshot.
• add issue-rating: 🦞 diamond lobster: Current issue advisory state selects this label.
• add clawsweeper:source-repro: Current issue advisory state selects this label.

Label justifications:

• P2: A source-supported parsing defect prevents usage display for one supported provider's monthly Individual plans.
• impact:auth-provider: Authenticated Qwen Cloud Individual accounts cannot obtain a usable provider usage snapshot.

Evidence reviewed

What I checked:

• Current parser excludes monthly-only responses: The shared personalUsage parser searches only for per5HourPercentage and per1WeekPercentage and requires one of those values. Neither monthly usage nor its reset is represented in the current shared snapshot. (Sources/CodexBarCore/Providers/Shared/AliyunOneConsole/OneConsoleTokenPlanSnapshot.swift:131, 8a146258a26d)
• Reported error follows the fallback path: QwenCloudUsageParser falls back to Alibaba subscription-summary parsing when personalUsage returns nil. That fallback throws Missing token plan data when the response lacks its legacy quota and subscription fields, matching the report. (Sources/CodexBarCore/Providers/QwenCloud/QwenCloudUsageParser.swift:21, 8a146258a26d)
• Established Individual provider contract: The provider documentation explicitly supports Individual token-plan subscriptions. Existing Qwen tests exercise nested and stringified usage envelopes, percentage conversion, reset dates, and legacy quota fallback; shared tests preserve separate Qwen and Alibaba identities. (docs/qwen-cloud.md:10, 8a146258a26d)
• Latest release remains affected: The v0.65.0 shared snapshot has the same five-hour/weekly-only recognition guard. No monthly fix is present in the inspected release or current main. (Sources/CodexBarCore/Providers/Shared/AliyunOneConsole/OneConsoleTokenPlanSnapshot.swift:132, 20a70d955d47)
• Open shared-parser fix candidate: fix(alibaba): parse Token Plan monthly usage window #3903 is open and adds per1MonthPercentage/per1MonthResetTime handling, monthly snapshot fields, and monthly-only primary-window projection in the exact shared code Qwen consumes. Its attached before/after transcript exercises Alibaba on Linux; it does not establish Qwen macOS display behavior. (Sources/CodexBarCore/Providers/Shared/AliyunOneConsole/OneConsoleTokenPlanSnapshot.swift, 884908009497)
• Related reports have different scope: The owner confirmed original Personal support landed through feat(providers): add Qwen Cloud individual token-plan provider #2361 in the discussion of Qwen Cloud Token Plan (Personal/Solo) uses a different API than the Team-edition provider, and Linux gating blocks it #2328. The recent owner comment on Qwen Cloud Team Token Plan support (GetSeatSubscriptionSummary) #3711 confirms Team support still needs a separate GetSeatSubscriptionSummary request and account-selection work; it is not this monthly Individual parser defect.

Likely related people:

• steipete: Suggested for follow-up; no historical authorship or introduction is verified. (role: unverified routing candidate; confidence: low)
• umutkeltek: Suggested for follow-up; no historical authorship or introduction is verified. (role: unverified routing candidate; 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.

[steipete]

#3931 (now landed on main) adds shared support for per1MonthPercentage, per1MonthResetTime, and monthly quota totals, with Qwen parser and menu tests. To confirm this issue matches that shape, please share a redacted response from personal/api/v2/usage, plus subscription/quota-config responses if relevant. Remove cookies, tokens, and account identifiers; representative numeric values are fine. Keeping this open until the response shape is confirmed.

[steipete]

Monthly-only and mixed rolling/monthly responses are supported by 79db9dc, incorporating the work from #3903/#3931. Thanks @Josephur for the original monthly-window work. The original response still needs to be checked against that implementation before this issue can be considered resolved.

[steipete]

Closing as fixed: Qwen Cloud Individual monthly usage is parsed since the monthly Token Plan support in #3903/#3931, which shipped in 0.68.0. #4046 then added tests with the exact envelope keys and monthly values from this report, covering both plausible inner DataV2 wrappers since the original nesting wasn't in the paste. Both parse, keep the reset time, and render as Monthly. This is proven against the reported response shape rather than a live account, so if 0.68.0 still shows a parse error for you, please reopen with the new error text. Thanks @Josephur for the report and @vincent-peng for the coverage!