Skip to content

Scope completion notifications to direct children #2461

@gwusi

Description

@gwusi

Describe the feature or problem you'd like to solve

Orchestrating agents receive completion noise from their entire descendant tree, not just direct children

Proposed solution

Completions should propagate one level: each agent receives signals only from its direct children. An orchestrator launching 8 sub-agents gets 8 completion signals regardless of how much nested work each spawns — keeping it focused on its own layer and reducing context noise from work it didn't directly delegate.

Example prompts or workflows

  1. An orchestrator runs 8 sub-agents, each using explore agents internally — it receives ~40–50 notifications today when 8 is all it needs.
  2. A sub-agent runs shell commands; each completion fires a notification to the orchestrator even though it has no use for them.
  3. Orchestrator → coordinators → workers: the orchestrator should hear from coordinators only, not from workers two levels down.

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    No fields configured for Feature.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions