docs: Update using modes and boomerang tasks documentation to include…

[hannesrudolph]

… Orchestrator mode details

---

Important

Updates documentation to include the new built-in Orchestrator mode, replacing the custom Boomerang Mode setup.

• Documentation Updates:
  • Adds Orchestrator mode details to using-modes.md, describing its purpose, tool access, and ideal use cases.
  • Updates boomerang-tasks.mdx to reflect that Orchestrator mode is now built-in, removing the need for custom setup.
  • Modifies custom-modes.md to include orchestrator in the list of default modes that can be overridden.

^{This description was created by for 3ff975b. You can customize this summary. It will automatically update as commits are pushed.}

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
roo-code-docs	🔄 Building (Inspect)	Visit Preview	💬 Add feedback	Apr 26, 2025 4:49am

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to 3ff975b in 1 minute and 20 seconds. Click for details.

• Reviewed 233 lines of code in 3 files
• Skipped 0 files when reviewing.
• Skipped posting 9 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. docs/basic-usage/using-modes.md:6

• Draft comment:
  The updated examples and mode names with emojis are clear. Ensure consistency in naming conventions (e.g., 🏗️ Architect, 💻 Code).
• Reason this comment was not posted:
  Confidence changes required: 10% <= threshold 50% None

2. docs/features/boomerang-tasks.mdx:27

• Draft comment:
  The new section correctly describes the built-in Orchestrator mode. Verify that all cross-references (e.g., anchor links) match actual targets.
• Reason this comment was not posted:
  Confidence changes required: 10% <= threshold 50% None

3. docs/features/custom-modes.md:156

• Draft comment:
  Updated text for overriding default modes now includes orchestrator. Ensure the JSON examples and inline comments conform to documentation style guidelines.
• Reason this comment was not posted:
  Confidence changes required: 10% <= threshold 50% None

4. docs/basic-usage/using-modes.md:6

• Draft comment:
  Consider verifying that the updated mode names and icons (e.g. 💻 Code, 🏗️ Architect, 🪃 Orchestrator) are used consistently throughout this document. This helps maintain uniformity in our UI references.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

5. docs/features/boomerang-tasks.mdx:27

• Draft comment:
  The update clarifies that the Orchestrator Mode is built-in and replaces the custom Boomerang Mode. Ensure that all internal references (including footnotes [^1] and [^2]) consistently reflect this change.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

6. docs/features/custom-modes.md:242

• Draft comment:
  The section on overriding default modes now includes 🪃 Orchestrator (aka Boomerang Mode). Please confirm that the JSON examples and descriptive text match the updated display names consistently.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

7. docs/basic-usage/using-modes.md:5

• Draft comment:
  There appears to be a typographical error in the admonition block syntax on line 5 (and closing on line 7): it uses four colons ("::::info Sticky Models") instead of the expected three colons (":::info Sticky Models"). Please correct this to ensure consistency with the project's markdown standards.
• Reason this comment was not posted:
  Comment was on unchanged code.

8. docs/features/boomerang-tasks.mdx:27

• Draft comment:
  Typo: The info admonition block starts with '::::info'. It should use ':::info' (three colons) according to the standard syntax.
• Reason this comment was not posted:
  Comment was on unchanged code.

9. docs/features/boomerang-tasks.mdx:58

• Draft comment:
  Typo: The tip admonition block starts with '::::tip'. Please correct it to ':::tip' (three colons) to adhere to standard markdown syntax.
• Reason this comment was not posted:
  Comment was on unchanged code.

Workflow ID: wflow_7vMq9GxO58xXsXy7

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}