Skip to content

[Feature]: Improve Control UI for Multi-Agent + Subagent Orchestration (Hierarchy, Bulk Ops, and Scalability) #52803

Description

@Leeon-K

Summary

Improve Control UI to support scalable multi-agent orchestration with clear agent-subagent hierarchy, active-first visibility, and efficient bulk operations.

Problem to solve

When multiple agents and subagents run concurrently, Control UI becomes hard to operate at scale.

Current views are too flat, so parent-child relationships (agent -> main session -> subagent tasks) are not clear. Operators must switch contexts frequently to track status and failures, and session history quickly creates noise. This makes concurrent management (kill/steer/retry) slow and error-prone.

Proposed solution

Add a dedicated orchestration view (Mission Board / Orchestration Panel) with:

  • Hierarchical view: Agent -> Main Session -> Subagent Sessions/Tasks
  • Active-first filters: running / failed / completed + history toggle
  • Bulk actions: multi-select + kill / steer / retry / cleanup
  • Per-row status info: model, elapsed time, status, last update
  • Scalable rendering for large session counts (virtualized list/tree)

Acceptance targets:

  • 50+ concurrent subagent sessions remain readable
  • Parent-child mapping visible without manual lookup
  • Bulk kill/steer in ~3 clicks

Alternatives considered

CLI workflows (/subagents list/info/log/kill/steer, /focus) are useful but high-friction for continuous orchestration.

Manual naming/filter conventions help partially, but do not solve hierarchy visibility or batch operation efficiency.

Impact

Affected:

  • Multi-agent users operating via Control UI (dashboard-v2)

Severity:

  • Medium to High (not a hard blocker, but major efficiency loss at scale)

Frequency:

  • Daily in multi-agent setups

Consequence:

  • Slower intervention on failed/stuck tasks
  • More context-switching and manual overhead
  • Lower orchestration throughput

Evidence/examples

Related issues:

Observed in real usage on OpenClaw 2026.3.13.

Additional information

This request was consolidated through joint investigation by OpenClaw assistant and the user, based on real multi-agent usage.

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Normal backlog priority with limited blast radius.clawsweeper:fix-shape-clearClawSweeper found a clear likely implementation shape for this issue.clawsweeper:needs-maintainer-reviewClawSweeper marked this issue as needing maintainer review before automation.clawsweeper:needs-product-decisionClawSweeper marked this issue as needing a product or behavior decision.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.clawsweeper:source-reproClawSweeper found a high-confidence source-level issue reproduction.enhancementNew feature or requestimpact:session-stateSession, memory, transcript, context, or agent state can drift or corrupt.issue-rating: 🦞 diamond lobsterVery strong issue quality with high-confidence source-level or clear reproduction.

    Type

    No type

    Fields

    Priority

    None yet

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions