Skip to content

[ENHANCEMENT] Orchestrator: choose subtask mode before approval #6706

@insight-automate

Description

@insight-automate

Type

Enhancement

Problem / Value

When Orchestrator proposes a new subtask, it sometimes selects the wrong mode. Fixing this today requires rejecting and re-instructing (adds noise) or accepting, canceling, editing, and resuming (extra steps). A quick pre-approval mode selection would reduce back-and-forth and save tokens.

Proposal

  • During the “Create subtask” prompt (e.g., “Roo wants to create a new subtask in 🖥️ Code mode”), allow the user to change the subtask’s mode via a clickable selector before approving.
  • The parent conversation remains in Orchestrator mode; only the pending subtask’s mode is adjusted.

Acceptance Criteria

  • Subtask creation UI includes a mode selector that’s active before approval.
  • Selected mode is applied to the subtask upon creation.
  • No change to the current conversation’s mode or the existing global mode selector.
  • Minimal extra clicks; default remains the agent’s suggested mode.

Notes

Keep the interaction lightweight and consistent with existing Orchestrator approval flows.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Issue - Needs ScopingValid, but needs effort estimate or design input before work can start.enhancementNew feature or requestfeature requestFeature request, not a bugproposal

    Type

    No type

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions