Parent reports completion while a native subagent is still working
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 18/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- typescript
Línea de trabajo
This is a design-level issue about the native subagent lifecycle in the OpenCode TUI: a parent turn can finalize while a required child is still running, and the late child report triggers another assistant reply. Start by reading the agent/subagent orchestration and tool-lifecycle code in the TypeScript repository, then trace where a parent turn decides it is complete relative to pending child sessions. A fix likely needs a pending-work state or a native wait/join mechanism; done means a parent cannot commit and report completion while a required child is outstanding, and a late child report does not wake a finished parent.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Description
In the OpenCode TUI, the parent committed its changes and sent a final “done” report while a native subagent was still working. The subagent later sent its first <subagent state="completed"> report, which woke the parent and resulted in a second assistant reply without another user prompt.
In the latest case, the parent assigned one new code-fixer session a test file and a syntax check. The parent owned implementation and final integration testing. They shared the workspace, so the parent could see the test file, run the full integration suite successfully, and commit before the child reported back. The child was still trying its own database test when the parent declared the work complete. Code edits were disjoint. Syntax checks and execution of the new cases overlapped.
I expect the parent to be able to yield while a required child runs, then review its report before committing or declaring the task complete. A pending-work state or a native wait/join option would make this reliable without polling and would still allow independent parent work in parallel.
Plugins
Oh My OpenCode Slim was disabled for this occurrence. The server config declares plugins: []. Local plugin files are present for Herdr agent state, Magpie model integration, and RTK. The CLI config enables the Herdr plugin. A run with all local plugins disabled is still pending.
OpenCode version
opencode v2.3.2 (V2 CLI/TUI). Parent model route magpie/auto/gpt-6.2-sol. Configured child route magpie/group/auto-deepseek-flash#high.
Steps to reproduce
- Use a global
AGENTS.mdthat delegates bounded work to native subagents, assigns non-overlapping files, and makes the parent responsible for reviewing results and final verification. My configuration definescode-fixer,designer,fast-generic,oracle, andrepo-scout. The affected turn used onlycode-fixerin a fresh child session. My rules call for fresh sessions for independent tasks and reuse only for follow-ups to the same task. - Ask the parent to finish a change. Have it delegate a regression test and syntax check to the child while implementing the production change itself. The child writes its file and continues checking it.
- Let the parent run integration checks after the child's file appears. In the observed turn, the parent then committed and reported completion before the native child report arrived.
- Leave the session open without sending another prompt. Observe the late child report and the additional parent reply. Similar premature “done” reports have occurred repeatedly in my workflow. These steps describe the observed case, and I have not established a deterministic minimal reproduction.
Related reports
My earlier Slim report documented repeated replays of previously delivered results. The latest occurrence involved one late first delivery from the native tool. I would like to understand whether OpenCode can support waiting for required child results before a parent finalizes. This may involve model behavior as well as the native tool lifecycle. OMO Slim #1940 · OpenCode #63785 · OpenCode #64073
Operating System
macOS 13.3 (Darwin 22.4.0, x86_64).
Terminal
OpenCode TUI in Herdr, TERM=xterm-256color, COLORTERM=truecolor, /bin/zsh.
- Lenguaje dominante
- TypeScript
- Estrellas
- 227k
- Forks
- 30.7k
- Merge medio
- 3 h 57 min
- PR fusionados (30 d)
- 484
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de anomalyco/opencode
-
[Site] Active section detection should respect scroll-margin-topPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abiertoarea/web reproduced type/bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
anomalyco/opencode#65384 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
area/cli type/feature version/v2
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
anomalyco/opencode#65379 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Shell tool: no upper bound on the timeout a model can ask for, so one call can hold a turn for hoursAbiertoarea/core platform/linux type/feature version/v2
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
anomalyco/opencode#65254 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
inference/go type/feature
Dificultad 1/5 1-3 horas Aptitud para principiantes 72/100
anomalyco/opencode#65148 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
area/providers type/feature version/v2
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
anomalyco/opencode#64845 · 1 comentario ·
Los mantenedores suelen responder en 1 día
Todos los issues de anomalyco/opencode
Issues similares
-
[Provider] antigravity-acp catalog omits gemini-4-hydrogen and gemini-4-neon that agy acp offersPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abiertocatalog provider provider-compatibility
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
lidge-jun/opencodex#9037 · 1 comentario · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
Project submission: xmcp DocsAbierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 62/100
slavakurilyak/awesome-ai-agents#1005 ·
-
kind/bug triage/unresolved
Dificultad 2/5 1-3 horas Aptitud para principiantes 60/100
Los mantenedores suelen responder en 1 día
-
effort:S P3 refactor
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
nightscout/nocturne#3735 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
wpilibsuite/systemcore-blocks-interface#641 ·
Los mantenedores suelen responder en 2 días