[Bug]: Multiple delegated subagents can remain stuck in Delegating without registering all children
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 48/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- typescript
- 领域
- cli
调研方向
Start with the CLI interactive TUI delegation/task projection and the local runtime session state, then reproduce the three independent read-only delegation calls described in the issue. Trace how each child is dispatched and registered; done means every requested child has a stable visible runtime status and the parent does not remain indefinitely in Running with unresolved Delegating rows.
由索引模型根据 Issue 内容生成。
描述
Product or interface
CLI - interactive TUI
Version
0.5.2
Platform
Linux
OS version and architecture
Ubuntu x64
Issue area
Agent stuck / slow / repeated loop; UI / UX
Steps to reproduce
- Start
mcodeand ask the main agent to split three independent, read-only audits into threeexploresubagents in the same turn. - Let the main agent emit the three delegation calls.
- Observe the TUI delegation/task projection and the local runtime session state.
Expected and actual behavior
Expected: Each independent delegation is either started concurrently or placed in an explicit visible queue. Every requested child gets a stable runtime session/status, and the parent does not remain indefinitely in Running with unresolved Delegating rows.
Actual: The TUI shows multiple Delegated/Delegating rows, but the runtime does not register all children as independent active sessions. In the reproduction, the first child was created and later became idle; the second child was created roughly 18 minutes later; the third requested child never appeared as a runtime child session. The parent remained Running, while the task summary showed 2 failed, 1 agent active, and 4 cancelled, with no actionable error explaining the undelivered third delegation.
This looks like a delegation dispatch/registration or observability bug rather than a model-quality issue. It is reproducible with independent read-only tasks and does not require parallel writers or shared-file conflicts.
Redacted error summary
No panic or stack trace. The observable state is:
Delegated (explore · audit A)
Delegating (explore · audit B)
Delegating
Tasks: 2 failed · 1 agent active · 4 cancelled
Parent: Running
Runtime children: first -> idle, second -> started much later, third -> absent
Additional context
- The repository already has feature discussions about scheduling and parallel subagents (#357 and #366). This report is specifically about the current observable behavior when the main agent issues multiple independent delegation calls: the TUI claims delegation activity that is not reflected consistently in runtime state.
- No credentials, private paths, account data, or raw session logs are included.
- 主要语言
- TypeScript
- 星标
- 2.1k
- 派生
- 271
- 平均合并
- 14 小时 23 分钟
- 30 天内合并 PR
- 35
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
MiniMax-AI/minimax-code 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 76/100
MiniMax-AI/minimax-code#556 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
MiniMax-AI/minimax-code#507 ·
维护者通常 1 天内回复
-
bug needs-triage tui
难度 2/5 1-3 小时 新手友好度 72/100
MiniMax-AI/minimax-code#481 · 1 条评论 ·
维护者通常 1 天内回复
-
bug cli documentation needs-triage
难度 2/5 1-3 小时 新手友好度 84/100
MiniMax-AI/minimax-code#299 · 3 条评论 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 54/100
MiniMax-AI/minimax-code#567 ·
维护者通常 1 天内回复
查看 MiniMax-AI/minimax-code 的全部 Issue
相似的 Issue
-
bug triage
难度 2/5 1-3 小时 新手友好度 74/100
维护者通常 1 天内回复
-
hemi-earn
难度 2/5 1-3 小时 新手友好度 82/100
vetro-protocol/vetro-monorepo#1043 ·
维护者通常 1 天内回复
-
stage 2: bare names resolve against PATH differently from the shell (empty and relative entries)未关闭
难度 2/5 1-3 小时 新手友好度 82/100
STRML/omp-classifier#206 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 70/100
atlassian-labs/mermaid-diagrams-viewer#188 ·
维护者通常 1 天内回复
-
dashboard enhancement
难度 2/5 1-3 小时 新手友好度 76/100
Olanetsoft/agent-lookout#225 ·
维护者通常 1 天内回复