agent超时后，即使跑完也无法更新给主对话 || After the agent times out, it cannot be updated to the main conversation even if it finishes running.

What version of Kimi Code CLI is running?

vscode plugin 0.5.7

Which open platform/subscription were you using?

subscription

Which model were you using?

No response

What platform is your computer?

No response

What issue are you seeing?

agent分配一个复杂任务，毫无悬念超时，然后自己继续吭哧吭哧干活，冗余动作一堆，agent返回了结果，即使暂停对话，让查看超时agent的输出也看不到，只能完整继续重新分析

What steps can reproduce the bug?

给agent分配长任务，超时，所有任务内容白做

What is the expected behavior?

让对话能看到超时agent返回的结果，以及允许设置更长的agent时间，还有，对agent运行时间的估算要合理，以及，agent超时本身的逻辑也有问题，超时并不是agent挂了，如果正常运行任务，可以继续等待，而不是直接无视，继续任务

Additional information

No response

---

What version of Kimi Code CLI is running?

vscode plugin 0.5.7

Which open platform/subscription were you using?

subscription

Which model were you using?

No response

What platform is your computer?

No response

What issue are you seeing?

The agent assigns a complex task and times out without any suspense. Then it continues to work on its own, with a lot of redundant actions. The agent returns the results. Even if the conversation is paused and the output of the timeout agent is viewed, the output of the timeout agent cannot be seen. It can only continue to re-analyze completely.

What steps can reproduce the bug?

Assigning long tasks to the agent will time out and all task content will be wasted.

What is the expected behavior?

Allow the dialogue to see the results returned by the timeout agent, and allow to set a longer agent time. In addition, the estimate of the agent running time must be reasonable, and there is also a problem with the logic of the agent timeout itself. Timeout does not mean that the agent has hung up. If the task is running normally, you can continue to wait, rather than directly ignoring it and continuing the task.

Additional information

No response

Start by reproducing the issue in the VS Code plugin 0.5.7 with a long-running agent task and observe what happens after timeout. Trace how the timeout, agent output, and main conversation interact; done means completed output remains visible and a normally running task is not discarded solely because its timeout elapsed.