MoonshotAI / MoonshotAI/kimi-code

[Bug] 扩展 0.7.5 更新后额度消耗异常:两个问题未答完已消耗 30%,5 小时窗口仅够 6–7 个问题

Open
#3,781 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
TypeScript
Stars
7.5k
Forks
1.2k
Avg merge
11h 53m
Merged PRs (30d)
350

Description

你运行的 Kimi Code 版本是?

VS Code 扩展 moonshot-ai.kimi-code 0.7.5

你使用的是哪个开放平台/订阅?

Kimi 会员订阅(Allegretto 年费),登录时选择的 Kimi 账号

你使用的是哪个模型?

K3

你的电脑平台是?

Microsoft Windows NT 10.0.26200.0 x64

你遇到了什么问题?

此前同样的使用方式下额度消耗正常。最近扩展自动更新到 0.7.5(扩展市场显示约 2 周前更新)
后,消耗速度异常放大:在 VS Code 中打开项目代码文件夹进行问答,两个问题尚未回答完毕,
5 小时滚动窗口额度已消耗约 30%。照此速度,一个 5 小时窗口仅能支撑 6–7 个问题,产品基
本丧失使用价值。目前 7 天周期额度也已 100% 耗尽,加油包未开启。

Image
复现步骤?
  1. VS Code 扩展自动更新至 Kimi Code 0.7.5;
  2. 打开一个项目代码文件夹(纯代码文件,无大型数据文件);
  3. 就项目代码连续提问 2 次;
  4. 查看账号额度页:5 小时窗口消耗约 30%,明显高于更新前水平。
期望的行为是什么?
  1. 消耗恢复至更新前水平;
  2. 排查 0.7.5 是否引入上下文重复发送、项目文件重复读取等回归问题;
  3. 建议每次请求发送前显示预估额度消耗,并在账号页提供逐次请求的消耗明细。
补充信息

附件为额度页面截图(5 小时窗口、7 天周期消耗)。如确认是版本回归,希望提供回退方案
或额度补偿。

Image
Contribution
  • 我愿意自己提交修复此 bug 的 PR(请先等待维护者在本 issue 中批准)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the report with the VS Code extension moonshot-ai.kimi-code 0.7.5 on Windows, using a code-only project and two questions, then compare the account's 5-hour and 7-day quota usage. Investigate whether context or project files are sent repeatedly; done means usage returns to the pre-0.7.5 level or the regression is isolated with evidence.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.