[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 摘要。