Qoder: Teams accounts show no member quota and miss organization resource packages
メンテナーはふだん 1 日以内に返信
評価
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 初心者へのやさしさ
- 52/100
- issue の種類
- 機能追加
- 明瞭さ
- 明確に書かれている
- 活発さ
- 活発
- 技術スタック
- swift
調査の方向性
Start by reading the existing Qoder provider implementation from #1736 and the Warp add-on credit precedent in #3634. Compare the member credit response with the organization-shared usage or usage presentation response described here, keeping the member-visible shared quota separate from the organization-wide pool. Done means Teams accounts show distinct credit pools, use the plan refresh time and exhaustion status, and personal accounts retain the existing member summary.
索引モデルが issue の本文から書いたものです。
説明
Summary
CodexBar's Qoder provider reads only the member credit endpoint. On a Qoder Teams/organization account, that response reports no member quota, so CodexBar shows a zero quota while Qoder's own Settings → Usage page shows a non-zero organization resource package (the shared add-on credit pool).
This is the Teams/organization surface of the existing Qoder provider, not a new provider.
Environment
- CodexBar 0.84.1 (current main)
- macOS 27.x, Apple Silicon
- Provider: Qoder, site
qoder.com(international), browser cookie session - Account type: Teams / organization
- Qoder web: Settings → Usage
Steps to reproduce
- Sign in to
qoder.comwith a Teams account that has an organization resource package. - Enable Qoder in CodexBar with Automatic or Manual browser cookies.
- Refresh Qoder.
- Compare CodexBar with Settings → Usage on the Qoder website.
Expected
- Show the organization resource package / add-on credits (used, cap, remaining, percentage).
- Use the plan's refresh date, not the stale reset carried by the member response.
- Keep plan and add-on pools distinguishable.
- Do not report exhausted while any pool has remaining credits.
Actual
- CodexBar shows a zero quota for Qoder.
- No resource-package / add-on row.
- The reset date comes from the member response and is stale.
Data sources (redacted)
All requests used the existing browser cookie session.
| Request | Observed shape |
|---|---|
Member credit endpoint (/api/v2/me/usages/big_model_credits) |
all member pools (plan_quota, resource_package_quota, dedicated_resource_package_quota, total_quota) report no quota |
Organization-shared usage endpoint (/api/v1/me/organization-shared-usages/big_model_credits) |
shared_quota with a non-zero used/cap/remaining; separate organization_pool |
Usage presentation endpoint (/sash/api/v2/me/usage) |
displayMode: "qoder"; userQuota empty; orgResourcePackage non-zero; expiresAt / refreshAt = plan refresh; isQuotaExceeded: false |
Redacted response shape (non-zero values replaced with placeholders):
{
"displayMode": "qoder",
"qoderUsage": {
"userType": "<account type>",
"usageType": "credits",
"isQuotaExceeded": false,
"expiresAt": "<plan refresh timestamp>",
"refreshAt": "<plan refresh timestamp>",
"userQuota": {
"total": 0,
"used": 0,
"remaining": 0,
"percentage": 0,
"unit": "credits"
},
"orgResourcePackage": {
"cap": "<non-zero cap>",
"used": "<non-zero used>",
"remaining": "<non-zero remaining>",
"percentage": "<fraction 0-1>",
"unit": "credits",
"available": true
},
"isPlanQuotaProrated": false
}
}
orgResourcePackage.percentage is a fraction (0–1), not a percentage.
Proposed fix
- Keep the current member endpoint as the fallback.
- Add an optional same-origin request to the organization-shared usage endpoint or the usage presentation endpoint, using the existing cookie.
- Surface
orgResourcePackage/addOnQuota/dedicatedResourcePackagesas additional credit windows; do not silently merge them into a zero plan. - Use the plan refresh timestamp for the reset and
isQuotaExceededfor exhaustion. - For personal accounts, continue using the existing member summary.
Scope
- Data-coverage fix for the existing Qoder provider, not a new provider.
- Uses the existing browser cookie session; no new credential type.
- Do not display the org-wide pool as the member's quota; use the member-visible shared quota.
- Enterprise display mode can be a follow-up if needed.
Related
- #1590 — original Qoder provider request; the maintainer asked whether this covers the individual dashboard or the Teams API.
- #1736 — Qoder provider implementation; folds
sharedQuotaonly when it appears in the member response. - #4686 — Qoder CN support.
- #3634 — Warp add-on credits precedent.
- 主要言語
- Swift
- スター
- 23.3k
- フォーク
- 2.2k
- 平均マージ
- 1日 18時間
- マージ済み PR(30日)
- 231
環境構築
このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
steipete/CodexBar のほかの issue
-
clawsweeper:needs-maintainer-review clawsweeper:no-new-fix-pr impact:other issue-rating: 🦪 silver shellfish P2
難易度 1/5 1時間未満 初心者へのやさしさ 72/100
steipete/CodexBar#5147 · コメント 1 件 · リアクション 1 件 ·
メンテナーはふだん 1 日以内に返信
-
googledeveloper: unclaimed Ultra credit (null remaining amount) fails with "unrecognized response" instead of "Not applied"対応中かも @djbclark が今日担当しました。 オープンclawsweeper:linked-pr-open clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster P2
難易度 2/5 1〜3時間 初心者へのやさしさ 28/100
steipete/CodexBar#5145 · コメント 1 件 · リアクション 1 件 ·
メンテナーはふだん 1 日以内に返信
-
clawsweeper:needs-maintainer-review clawsweeper:no-new-fix-pr impact:other issue-rating: 🦪 silver shellfish P2
難易度 3/5 1〜2日 初心者へのやさしさ 50/100
steipete/CodexBar#5144 · コメント 1 件 · リアクション 1 件 ·
メンテナーはふだん 1 日以内に返信
-
Claude CLI source drops "Current week (all models)" when /usage redraws over earlier screen contentオープンclawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P2
難易度 4/5 3〜5日 初心者へのやさしさ 30/100
steipete/CodexBar#5143 · コメント 1 件 · リアクション 1 件 ·
メンテナーはふだん 1 日以内に返信
-
clawsweeper:needs-info clawsweeper:needs-maintainer-review clawsweeper:no-new-fix-pr impact:ux-friction issue-rating: 🦐 gold shrimp P2
難易度 4/5 3〜5日 初心者へのやさしさ 42/100
steipete/CodexBar#5132 · コメント 5 件 · リアクション 1 件 ·
メンテナーはふだん 1 日以内に返信
steipete/CodexBar の issue をすべて見る
似ている issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
nwverse/persona#12800 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
bug documentation
難易度 1/5 1時間未満 初心者へのやさしさ 86/100
ajithrnayak/xpunge#7 ·
-
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
-
難易度 1/5 1時間未満 初心者へのやさしさ 65/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
DuarteSantos8/openGym#1469 ·
メンテナーはふだん 2 日以内に返信