[compound-engineering] Observation: parent thread did not continue supervising delegated subagent

Abierto
#839 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
typescript

Línea de trabajo

Start by locating the agent orchestration and subagent delegation guidance for Codex workflows; the issue gives the plugin version and describes the expected parent behavior but names no files or tests. Check whether existing guidance covers tracking, waiting for, and integrating required subagent results, then identify how that behavior can be verified. Done means the parent remains responsible for downstream workflow steps or reports an explicit blocker.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Bug Description

Component: Agent orchestration / subagent delegation behavior
Summary: Observed one run where the parent thread dispatched a subagent, then treated dispatch as enough progress instead of actively waiting for the result, integrating it, and completing the merge/review workflow. This may be an intermittent drift rather than a deterministic bug.

Environment

  • Plugin Version: ecc-universal 1.10.0 (from local Codex plugin cache)
  • Agent Platform: Codex desktop / Codex CLI
  • Agent Version: codex-cli 0.120.0
  • OS: Darwin 25.3.0 arm64

What Happened

During a Compound Engineering workflow, the parent thread delegated work to a subagent for a design/review-related task. After dispatching, the parent thread gave the user an update that effectively sounded like the handoff itself was the outcome, without continuing to monitor the subagent, wait for the result, integrate the result into the active workflow, or drive the remaining review/merge steps.

The user had to point out that after dispatching a subagent, the parent thread should still supervise and own completion. In the next pass, the parent thread did correctly wait for the reviewer subagent, consume its result, write the review gate back to the MR, merge the MR, switch back to develop, pull latest, update/close the issue, and stop the dev server.

Expected Behavior

When the parent thread dispatches a subagent, it should keep ownership of the workflow until completion or an explicit blocker:

  1. Track the subagent status.
  2. Wait for the result when it is needed for the next decision.
  3. Validate and integrate the returned result.
  4. Continue the remaining workflow steps, such as writeback, merge, branch cleanup, issue updates, and final status.
  5. Avoid presenting “subagent dispatched” as equivalent to “task handled.”

Steps to Reproduce

This is reported as an observation, not yet a deterministic repro:

  1. Start a CE-style GitLab issue/MR workflow.
  2. Delegate a required design or reviewer gate task to a subagent.
  3. Observe whether the parent thread keeps supervising the subagent and completes the downstream workflow, or prematurely returns after dispatch.

Error Messages

No runtime error message was shown. The issue was behavioral/orchestration drift.

Additional Context

The observed failure mode is important because CE workflows rely on the parent/orchestrator thread to preserve accountability. Subagents can produce artifacts or review decisions, but the parent still needs to own integration, writeback, merge safety, and final repository state.

Suggested framing: this may be either a bug in orchestration guidance/tooling or an intermittent model behavior issue. It would be useful to clarify whether CE should include stronger explicit guidance that dispatching a subagent is never a terminal state for a workflow.


Reported via the report-bug-ce skill

Lenguaje dominante
TypeScript
Estrellas
25.6k
Forks
2.1k
Merge medio
3 h 57 min
PR fusionados (30 d)
170

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de EveryInc/compound-engineering-plugin

Todos los issues de EveryInc/compound-engineering-plugin

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.