Qwen Cloud Team Token Plan support (GetSeatSubscriptionSummary)

[tavioto]

Summary

CodexBar currently appears to support the Qwen Cloud Individual Token Plan, but not the newer Qwen Cloud Team Token Plan available directly at:

https://home.qwencloud.com/analytics/token-plan/team

I am using CodexBar 0.60.4 on macOS with an active Qwen Cloud Team subscription.

The Qwen Cloud provider successfully imports my Qwen Cloud browser session, but fetching usage fails with:

Failed to parse Qwen Cloud usage: Missing token plan data

This seems to happen because the Team plan uses a different API from the Individual plan.

Current plan

The subscription is a Qwen Cloud Team International plan.

Example plan information shown by the Qwen Cloud UI:

• Plan: Standard
• Seats: 1 / 1
• Credits: 25,000
• Remaining credits: ~6,374
• Product code: sfm_tokenplanteams_dp_intl
• Credits reset at the subscription cycle boundary

This is not an Alibaba Model Studio Team subscription. It is a Team subscription hosted directly on home.qwencloud.com.

Steps to reproduce

1. Sign in to a Qwen Cloud Team account at:

   https://home.qwencloud.com/

2. Open:

   https://home.qwencloud.com/analytics/token-plan/team

3. In CodexBar:

   • Enable Qwen Cloud
   • Leave Cookie source on Auto
   • Refresh usage

4. CodexBar successfully finds the browser session, but usage parsing fails with:

Failed to parse Qwen Cloud usage: Missing token plan data

API used by the Qwen Cloud Team dashboard

The Team dashboard retrieves the subscription/usage information using:

POST https://home.qwencloud.com/data/api.json?product=BssOpenAPI-V3&action=GetSeatSubscriptionSummary

Request Content-Type:

application/x-www-form-urlencoded

Query parameters:

product=BssOpenAPI-V3
action=GetSeatSubscriptionSummary

The form body sent by the official Qwen Cloud UI looks like this:

product=BssOpenAPI-V3
action=GetSeatSubscriptionSummary
sec_token=<redacted>
region=cn-hangzhou
language=zh-CN
params={"productCode":"sfm_tokenplanteams_dp_intl","Nbid":"<redacted>"}

Cookies from the existing Qwen Cloud browser session are also sent with the request.

Note that although the subscription is the International Team product:

sfm_tokenplanteams_dp_intl

the current Qwen Cloud frontend sends:

region=cn-hangzhou
language=zh-CN

for this request.

Sanitized response

The API returns a response like:

{
  "code": "200",
  "data": {
    "RequestId": "<redacted>",
    "Message": "Successful!",
    "Data": {
      "Uid": "<redacted>",
      "EndTime": 1790251200000,
      "ProductCode": "sfm_tokenplanteams_dp_intl",
      "StartTime": 1784894400000,
      "RemainingDays": "6",
      "SubscriptionGroupList": [
        {
          "SubscriptionAssignedNumber": 1,
          "EquityList": [
            {
              "EquityCode": "credit_value",
              "TotalValue": "25000.00000000",
              "EquityType": "CREDITS",
              "SurplusValue": "6373.93922996"
            }
          ],
          "SpecType": "standard",
          "SubscriptionTotalNumber": 1,
          "NextCycleFlushTime": 1790251200000
        }
      ]
    },
    "Code": "Success",
    "Success": true
  },
  "httpStatusCode": "200",
  "successResponse": true
}

Useful field mapping

Most of the data CodexBar needs appears to already be available directly in this response.

Plan / tier

SubscriptionGroupList[].SpecType

Example:

standard

Total credits

Find:

EquityList[].EquityCode == "credit_value"

Then use:

TotalValue

Example:

25000.00000000

Remaining credits

SurplusValue

Example:

6373.93922996

Used credits

Can be calculated as:

TotalValue - SurplusValue

For the sample above:

25000 - 6373.93922996 = 18626.06077004

Usage percentage

used / total

For the sample above:

~74.50%

Reset / next cycle

NextCycleFlushTime

This appears to be Unix time in milliseconds.

Subscription period

StartTime
EndTime
RemainingDays

Seats

SubscriptionAssignedNumber
SubscriptionTotalNumber

Product

ProductCode

Example:

sfm_tokenplanteams_dp_intl

Possible implementation direction

CodexBar already seems to have most of the infrastructure necessary for this.

The existing Qwen Cloud provider already handles:

• home.qwencloud.com
• Qwen Cloud browser cookies
• One Console authentication / sec_token
• Authenticated form-encoded requests
• Usage snapshots

The current Qwen Cloud implementation appears to target the Individual Token Plan APIs under:

tokenplan/personal/api/v2/*

The Team plan could potentially be detected/fetched separately using:

product=BssOpenAPI-V3
action=GetSeatSubscriptionSummary

There also appears to be similar infrastructure already in AlibabaTokenPlanUsageFetcher, which uses:

BssOpenAPI-V3
GetSubscriptionSummary

So GetSeatSubscriptionSummary for Qwen Cloud Team may be reusable within the existing One Console / BSS request infrastructure rather than requiring a completely new provider.

Conceptually:

Qwen Cloud
├── Individual Token Plan
│   └── existing personal/api/v2/* flow
│
└── Team Token Plan
    └── BssOpenAPI-V3 / GetSeatSubscriptionSummary

The Team parser could produce a usage snapshot from:

SubscriptionGroupList
  -> SpecType
  -> EquityList[EquityCode == "credit_value"]
  -> TotalValue
  -> SurplusValue
  -> NextCycleFlushTime

Expected behavior

When the Qwen Cloud account has a Team Token Plan, CodexBar should detect it and display something equivalent to:

Qwen Cloud
Standard Team

18,626 / 25,000 credits used
74.5%

6,374 credits remaining

Resets: <NextCycleFlushTime>
Seats: 1 / 1

The exact UI does not matter to me; the important part is being able to see the Team credit pool and reset information in CodexBar.

Actual behavior

CodexBar currently imports the Qwen Cloud session successfully but fails while parsing usage:

Failed to parse Qwen Cloud usage: Missing token plan data

The Alibaba Token Plan provider also does not solve this, because this subscription exists on:

home.qwencloud.com

rather than the Alibaba Model Studio / Bailian console.

Environment

CodexBar: 0.60.4
OS: macOS
Qwen product: Qwen Cloud Team Token Plan
Plan tier: Standard
Product code: sfm_tokenplanteams_dp_intl
Dashboard: https://home.qwencloud.com/analytics/token-plan/team

I can provide additional sanitized request/response samples or test the implementation against a live Team account if useful.

[clawsweeper]

Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve. Reviewed September 17, 2026, 9:54 AM ET / 13:54 UTC.

Summary
Team support remains a distinct, useful coverage request: current main and v0.60.4 still fetch Individual plan APIs. The sanitized response provides a strong starting point, while account discovery and subscription-selection behavior need clarification. Repository policy also prohibits automatic closure.

Reproducibility: not applicable. as an established-behavior bug: Team coverage is outside the documented Individual contract. Source confirms the missing Team fetch path; the reported account failure was not independently executed.

Ways to help us reproduce this

• Add a screenshot or short recording showing the behavior.
• Add expected vs actual behavior.

Maintainer decision needed

Question	Recommendation
Should the existing Qwen provider support Team credit pools, and which subscription should it display when an account has both Individual and Team plans?	Sponsor Team support within Qwen: Approve a Team strategy that preserves existing Individual results and defines mixed-plan selection after sanitized account-discovery evidence is available.

Why: The single-group capture establishes useful data, but does not determine account selection or mixed-plan presentation; these choices affect existing provider behavior.

Next step
Confirm subscription-selection policy and obtain sanitized Nbid-discovery and multiple-group evidence before commissioning implementation; this is new coverage rather than a strict bug repair.

Review details

Best possible solution:

Extend the existing Qwen provider with a Team-specific request and parser, preserve Individual behavior, and reuse shared credit-pool presentation with explicit subscription-selection rules.

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

Not applicable as an established-behavior bug: Team coverage is outside the documented Individual contract. Source confirms the missing Team fetch path; the reported account failure was not independently executed.

Is this the best way to solve the issue?

Yes, extending the existing Qwen provider is the narrowest direction because its snapshots already support credit pools; changing only the endpoint or reusing the generic parser would leave Team selection and reset semantics incomplete.

AGENTS.md: found and applied where relevant.

Remaining risk / open question:

• The sample does not establish how to discover Nbid from the authenticated Qwen session.
• Selection or aggregation across multiple subscription groups, differing reset dates, and accounts holding both Individual and Team plans remains unspecified.

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

Label changes

Label justifications:

• P2: This is a concrete, bounded provider-coverage improvement for an unsupported subscription type, without evidence of an existing supported workflow regressing.
• impact:auth-provider: The request concerns authenticated Qwen account discovery, subscription routing, and usage retrieval.

Evidence reviewed

What I checked:

• Current implementation remains Individual-only: The checkout matches fetched main. The fetcher declares the Individual product and three personal API endpoints, then executes those requests without a Team discovery or GetSeatSubscriptionSummary branch. (Sources/CodexBarCore/Providers/QwenCloud/QwenCloudUsageFetcher.swift:38, b6e65a83dc47)
• Established provider contract: Documentation explicitly limits Qwen coverage to Individual plans. Tests assert the Individual dashboard and personal usage endpoint; separate tests show that the existing snapshot can already render credit-pool totals, making shared presentation a plausible implementation path. (Tests/CodexBarTests/QwenCloudProviderTests.swift:121, b6e65a83dc47)
• Latest release has the same fetch boundary: Inspection of v0.60.4 shows the same Individual product and personal usage/subscription/quota-config endpoints; the release tag resolves to the supplied latest-release commit. (Sources/CodexBarCore/Providers/QwenCloud/QwenCloudUsageFetcher.swift:38, 937b20813cf4)
• Reporter supplies concrete Team contract evidence: The supplied issue body reports v0.60.4 session import succeeding and usage failing, and includes a sanitized GetSeatSubscriptionSummary request and response with a credit equity and NextCycleFlushTime. Nbid is redacted without describing its discovery, and the sample contains only one subscription group. This is reporter evidence, not an independently executed account probe.
• Legacy parser reuse is only partial: Qwen parsing can fall back to the Alibaba summary parser, whose aliases include TotalValue and SurplusValue. That parser does not explicitly select credit_value equities or recognize NextCycleFlushTime, so generic summary compatibility does not establish complete Team support. (Sources/CodexBarCore/Providers/Alibaba/AlibabaTokenPlanUsageFetcher.swift:911, b6e65a83dc47)
• Related merged work covers Personal plans: GitHub verifies feat(providers): add Qwen Cloud individual token-plan provider #2361 merged on July 28 and describes a first-class Individual provider. Owner discussion at Qwen Cloud Token Plan (Personal/Solo) uses a different API than the Team-edition provider, and Linux gating blocks it #2328 (comment) confirms Personal coverage. The mainland request Support 百炼 Token Plan Personal Edition (China mainland, rolling 5h/7d windows) #2355 was redirected to separate Personal/Solo work. These do not resolve this Team request. (83a7fd38a1f5)

Likely related people:

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

Thanks @tavioto for the detailed request and response. On 173afc88a417, Qwen Cloud still calls only the individual-plan APIs; the shared OneConsole parser work did not add GetSeatSubscriptionSummary. This issue remains unresolved.

The reported Team RPC requires application/x-www-form-urlencoded, while the current plugin HTTP host accepts JSON POST only and forces that content type. The next prerequisite is bounded form-POST support in the host. We also need a sanitized explanation of where the dashboard obtains Nbid, or evidence that this parameter can be omitted. No credential values are needed.

Once those prerequisites are established, Team parsing should select the credit_value equity within its subscription group, use NextCycleFlushTime for reset, and keep identity under Qwen Cloud. A valid Team summary should take precedence over personal usage, with personal usage retained when no active seat summary exists. No fix has landed yet.

[steipete]

Thanks @tavioto for the sanitized Team request and response. The sample provides 25,000 total credits, 6,373.93922996 remaining credits, and a cycle reset. The current Qwen fetcher calls Individual APIs only, while the plugin host supports JSON POST rather than the form POST required by GetSeatSubscriptionSummary. Team support needs that host capability plus a verified way to discover Nbid. This remains open; no native Team path was added.

[steipete]

Thanks @tavioto! Implemented in #4338 (merged as 9fae8c8): the Qwen Cloud Team Token Plan is read through GetSeatSubscriptionSummary, with the seller identity discovered from the console (no manual selector needed when discovery returns none). Ships in the next release; please try it on your team plan and report anything off in a new issue.