Boomerang Tasks

Free

Automatically turns big ideas into task queues.

FreeFree tier

Type

Open Source

Visit Website GitHub (38 stars)

About Boomerang Tasks

Boomerang Tasks is a built-in feature of Roo Code that enables orchestration of complex workflows by breaking projects into smaller, manageable subtasks. Using the dedicated Orchestrator mode, users can delegate each subtask to a specialized mode (such as Code, Architect, or Debug) that runs in its own isolated context with separate conversation history. The parent task pauses, and upon subtask completion, only a concise summary is returned to the orchestrator, keeping the high-level workflow uncluttered. This allows developers to tackle multi-step projects efficiently, leverage the best mode for each job, and automatically pass results between subtasks. Default approval for subtask creation and completion can be automated via Auto-Approving Actions, and the interface provides hierarchical navigation to track parent-child task relationships.

Key Features

Built-in Orchestrator mode for managing workflows

Break down large projects into focused subtasks

Delegate subtasks to specialized Roo Code modes (Code, Architect, Debug, etc.)

Each subtask runs in its own isolated context with separate conversation history

Parent task pauses and resumes with only the subtask summary

Automatic passing of results between subtasks

Default approval workflow with optional auto-approval

Hierarchical task navigation between active and paused tasks

Pros & Cons

Pros

Tackles complexity by breaking big ideas into manageable pieces
Leverages specialized modes for optimal results on each subtask
Isolated context prevents the orchestrator from being cluttered with detailed execution steps
Streamlines workflows by automatically passing results between subtasks
Built-in Orchestrator mode eliminates need for custom mode setup
Auto-approval option speeds up repetitive approvals

Cons

Orchestrator mode cannot read files, write files, call MCPs, or run commands by design (limits direct file manipulation)
Requires explicit information passing; subtasks do not automatically inherit parent context
Only the subtask summary returns to the parent; detailed execution history is lost
Default approval required for each subtask, which may slow down automated workflows unless auto-approval is enabled
Learning curve for effectively structuring complex workflows into subtasks

Best For

Building a full feature by splitting into design, implementation, and documentation subtasksAutomating complex multi-step development workflows (e.g., architecture → coding → testing)Managing large codebases with dedicated debugging or code review subtasksStreamlining iterative development cycles where each phase uses a specialized mode

FAQ

Why can't Orchestrator mode read files, write files, call MCPs, or run commands?

The Orchestrator mode is intentionally limited to focus on high-level workflow management. Giving it file access by default would fill its context with file reads, hampering its ability to remain focused on orchestration. Subtasks handle detailed work and return only necessary information via their summaries.

Do I need to approve each subtask creation and completion?

By default, you must approve the creation and completion of each subtask. This can be automated via the Auto-Approving Actions settings if desired.

How does context transfer between parent and subtasks?

Each subtask operates in complete isolation with its own conversation history. Information must be explicitly passed: down via the initial instructions when the subtask is created, and up via the final summary when the subtask finishes. Only that summary returns to the parent.