docs(agent): clarify stuck-subagent monitoring

This commit is contained in:
zap
2026-03-13 00:21:17 +00:00
parent 3bb3888340
commit 7669d5787d
2 changed files with 4 additions and 0 deletions

View File

@@ -13,3 +13,4 @@
- Conclusion: the immediate failure was caused by an incorrect explicit model selection in the spawn request, not by missing auth propagation between agents.
- Corrective action: retry fresh delegation with `litellm/glm-5` (the intended medium-tier routed model for delegated implementation work in this setup).
- Will explicitly requested on 2026-03-13 to use `gpt-5.4` for subagents for now while debugging delegation reliability.
- Will also explicitly requested that zap keep a light eye on active subagents and check whether they look stuck instead of assuming they are fine until completion.