MoonshotAI / MoonshotAI/kimi-code
subagents provider will not be changed when change provider in web UI AND some web ui bugs
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 7.5k
- Forks
- 1.2k
- Avg merge
- 11h 53m
- Merged PRs (30d)
- 350
Description
What version of Kimi Code is running?
0.36.1
Which open platform/subscription were you using?
api-key for kimi code subsription and a subscription using "/login"
Which model were you using?
K3 max
What platform is your computer?
Linux 6.18.33.2-microsoft-standard-WSL2 x86_64 unknown
What issue are you seeing?
subagents无法正确切换模型导致无法正确执行下去
在使用api-key启动session,使用kimi web,然后启动了suagents如下
在耗尽了我的第一份使用api key的订阅的时候,会自动停止,切换回用login登录的k3订阅重新continue的时候提示如图
后续模型会在主agent上完成subagents的未完成任务(但是我希望通过subagents完成的任务并没有完成,尝试恢复失败了模型就自己完成任务去了)
同时web这里显示的状态也是错误的,实际上这三个subagents其实都是stop但是没有刷新状态
What steps can reproduce the bug?
测试历程
在执行任务时使用subagents完成任务的过程中只要额度到了自动会停止(因为很难去尝试一次正好的额度用完,我会使用单纯的打断来模拟(我会列举更多的情况,因为我遇到了更加奇葩的问题)
windows环境下subagents的打断尝试
然后我主动打断
然后我主动提示恢复(这里恢复了之后我又打断了,这里subagent因为停止之后有一些状态是丢失的,比如tool计数重新开始,但是tok使用又是还有记录的,这比较抽象)
Linux环境 kimi web 打断尝试
这里我启动一个subagents工具后直接停止打断
后续我切换提供商openrouter的ds api继续对话,这里llm 应该是使用resume工具还是完成了恢复,但是web这里莫名其妙的多了一个状态,从头到尾只有一个subagent,同时subagent还是使用k3 high没有切换(这里存疑,但是从我遇到的问题上来看,确实是没有切换的)
这里我又撤回了“subagent可以恢复吗“对话(使用的已发送信息下方的撤回编辑),再重新发送了一次。subgent任务结束表现结果是撤回编辑无法撤回ui上新建的子agent。然后打断之后恢复的subagent状态也没有办法传过来导致UI上一直显示在运行。从头到尾应该只存在一个subagent,剩下这两个是虚空创建的UI
What is the expected behavior?
-
准确的来说,web的操作和terminal一致,但是这里是stop的之后的,所以我自认为切换模型之后应该是都切换了(就类似于现在这个情况,用户一旦quit那么subagent的状态全部丢失,浪费了token,任务也没有完成。那如果必须不切换模型,那我这个任务就必须等待额度刷新,而且不能莫名其妙的错点或者kill了后台。(所以考不考虑做subagent的生命周期管理?)
-
web ui很多功能确实很好,我从最初的web用过了,最近的一次大更新审美好了很多,但是功能还有些问题
Additional information
No response
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 provider switch and stop/resume flows in the web UI, comparing them with the terminal behavior described in the report. Trace how subagent provider selection and status updates are represented after interruption, continuation, and message withdrawal. Done means the selected provider is applied consistently and the web UI shows the actual subagent count and stopped or running states.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100