[Bug]: Show CLIProxyAPI limits in sidebar

未關閉
#39,751 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

@StiensWout 已經在處理了。

開始於 2026年11月20日。

  • #39752 來自 @StiensWout —— 未關閉

評估

難度
4/5
預估耗時
1-2 天
新手友好度
35/100
Issue 類型
缺陷
描述清晰度
基本清楚
活躍度
停滯
技術堆疊
typescript
領域
frontend

研究方向

The issue identifies apps/web as the affected area. Start by tracing how the sidebar reads subscription limits for CLIProxyAPI accounts and compare that with the context usage shown there. Reproduce with an account that exposes limits, then verify that available limits appear while genuinely unreadable limits remain unavailable.

由索引模型根據 Issue 內容生成。

描述

vouch:trusted
Before submitting
  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.
Area

apps/web

Steps to reproduce

When using CLIProxyAPI, usage does not seem to work in the T3 Code sidebar. The screenshot shows “Limits” as “Unavailable,” and hovering says “This account has no subscription limits,” while context usage displays 246k / 475k. Reproduce with a CLIProxyAPI-backed account that exposes subscription limits and fix the sidebar to show the available usage limits. Preserve the unavailable state for accounts where limits genuinely cannot be read.

Expected behavior

No response

Actual behavior

When using CLIProxyAPI, usage does not seem to work in the T3 Code sidebar. The screenshot shows “Limits” as “Unavailable,” and hovering says “This account has no subscription limits,” while context usage displays 246k / 475k. Reproduce with a CLIProxyAPI-backed account that exposes subscription limits and fix the sidebar to show the available usage limits. Preserve the unavailable state for accounts where limits genuinely cannot be read.

Impact

Minor bug or occasional failure

Version or commit

main

Environment

Not environment specific.

Logs or stack traces

No response

Workaround

No response

主要語言
TypeScript
星號
24.8k
分支
6.4k
平均合併
4 小時 29 分鐘
30 天內合併 PR
488

環境準備

在 Codespaces 中開啟

在瀏覽器裡用你自己的 GitHub 帳號啟動這個專案的開發容器。

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

pingdotgg/t3code 的其他 Issue

查看 pingdotgg/t3code 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。