MoonshotAI / MoonshotAI/kimi-code
在写计划时卡住 然后把额度耗光了
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 7.5k
- Forks
- 1.2k
- Avg merge
- 11h 53m
- Merged PRs (30d)
- 350
Description
你运行的 Kimi Code 版本是？
2.0.1
你使用的是哪个开放平台/订阅？
kimi code
你使用的是哪个模型？
k3-256k max
你的电脑平台是？
Microsoft Windows NT 10.0.26300.0 x64
你遇到了什么问题？
当我在修复一个项目bug时 模型刚开始很正常 但到了写计划这一步 一直写不完 我发送的继续 ? 在干啥呢等文字也没有反应 然后我以为是普通的卡住 就没管他 过了一个小时 报了403 显示我额度用完了 然后我看计划确实写了一部分 但很少根本不可能把我的5小时额度用光 我是199的订阅
复现步骤？
session_5f9018ef-bc01-41a4-a83e-ff1ee3d40733 上下文用完了
期望的行为是什么？
更新了2.0.0以后就经常卡住 但之前卡住就卡住了 这次怎么还把我额度消耗完了
补充信息
No response
Contribution
- 我愿意自己提交修复此 bug 的 PR（请先等待维护者在本 issue 中批准）
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the report with Kimi Code 2.0.1 on Windows using the k3-256k max model, focusing on session_5f9018ef-bc01-41a4-a83e-ff1ee3d40733 and the transition into plan writing. Determine why the session stops responding while continuing to consume quota; done means the hang is prevented or bounded and the behavior is covered by a verified reproduction.
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
- Needs clarification
- Newbie friendliness
- 38/100