MoonshotAI / MoonshotAI/kimi-code
Subagent panel shows completed subagents as "运行中" with ever-growing timers
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 7.5k
- Forks
- 1.2k
- Avg merge
- 11h 53m
- Merged PRs (30d)
- 350
Description
Summary
The task panel's subagent ("子 Agent") section shows completed foreground subagents as "运行中" (running) with ever-increasing elapsed timers, even though the subagents have finished and returned their results to the parent agent.
Environment
- kimi-code 0.36.0
- Windows 11 (MINGW64 / Git Bash)
- Session spanning multiple days (with context compaction and date changes)
Observed behavior
In the task panel's "子 Agent · 4 运行中" section, four foreground subagents are listed as running with elapsed timers at 54:50, 181:31, 194:14 and 222:00.
All four subagents had already completed: they ran in the foreground, returned their final reports to the parent agent, and the conversation continued normally based on those results (code changes delivered by the coder subagents are present, tested and committed).
Since subagents have a fixed 2-hour timeout, entries displaying 181–222 minutes prove the displayed status is stale — a genuinely running subagent would have been terminated at 120 minutes.
Note: background bash tasks in the same panel ("后台 Bash") correctly show their completed state; only subagent entries appear affected.
Expected behavior
A subagent entry transitions to a completed state when the subagent returns its result, instead of remaining "运行中" with the timer counting up indefinitely.
Reproduction
- In an interactive session, have the agent launch foreground subagents (e.g. explore/coder types) via the Agent tool.
- Wait for the subagents to return their results and the parent agent to continue.
- Open the task panel — the subagent entries still show "运行中" with timers counting.
Additional notes
The user reports this has occurred since they first started using the product, so it does not appear version-specific. Screenshot of the panel state is available on request.
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 at the Agent tool's foreground subagent lifecycle and trace how completion reaches the task panel. Compare it with the panel's correctly completed background Bash entries and inspect how the status and elapsed timer are rendered. Done means a returned subagent is shown as completed and its timer stops, including the reported reproduction case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100