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

Open
#839 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
typescript

Research direction

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.

Written by the indexing model from the issue text.

Description

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

Dominant language
TypeScript
Stars
25.6k
Forks
2.1k
Avg merge
3h 57m
Merged PRs (30d)
170

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from EveryInc/compound-engineering-plugin

All issues in EveryInc/compound-engineering-plugin

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.