[BUG] Architect mode attempts to create subtasks

[HitByBricks]

Problem (one or two sentences)

When using Architect mode, after it has formulated a plan, it's expected to switch modes to execute the plan. However, it instead attempts to create subtasks, which Is reserved exclusively for the Orchestrator mode.

Context (who is affected and when)

Happens to users creating tasks for Architect mode.

Reproduction steps

1. Any OS
2. Create task for Architect mode
3. Architect mode begins analyzing and creating plan as expected, then asks to create a subtask (unexpected).

Expected result

"Roo Code wants to switch modes"

Actual result

"Roo Code wants to create a subtask"

Variations tried (optional)

No response

App Version

3.47.0

API Provider (optional)

Google Gemini

Model Used (optional)

No response

Roo Code Task Links (optional)

No response

Relevant logs or errors (optional)

[roomote]

I've analyzed this issue and here's my proposed implementation plan:

Root cause: The new_task tool is listed in the ALWAYS_AVAILABLE_TOOLS array in src/shared/tools.ts (line 334), which makes it unconditionally available to ALL modes -- including Architect. While Architect mode's customInstructions explicitly tell the model to use switch_mode, the new_task tool is still present in the tool list, and some models (Google Gemini in this case) may choose to call it instead of switch_mode.

Proposed fix:

1. Remove new_task from ALWAYS_AVAILABLE_TOOLS in src/shared/tools.ts -- switch_mode stays, so all modes can still switch modes.
2. Add the "modes" group to modes that should retain new_task access in packages/types/src/mode.ts (DEFAULT_MODES):
   • Code -- add "modes" group (can delegate work via subtasks)
   • Debug -- add "modes" group (can delegate work via subtasks)
   • Orchestrator -- add "modes" group (primary user of new_task)
   • Architect -- do NOT add "modes" (should only use switch_mode)
   • Ask -- do NOT add "modes" (informational mode, no subtask creation needed)
3. Update affected tests to reflect the new tool availability per mode.

This approach:

• Keeps switch_mode available to all modes (it remains in ALWAYS_AVAILABLE_TOOLS)
• Makes new_task opt-in per mode via the existing modes tool group
• Aligns with the design intent where Orchestrator is the primary subtask creator
• Users with custom modes can still add the "modes" group to re-enable new_task
• Minimal code change with clear semantics

Please mention @roomote in a comment saying that you approve this plan, and I'll proceed with the implementation.

[HitByBricks]

@roomote I initially made a mistake, the version being used was 3.47.3, not 3.47.0. Don't approve the plan just yet.

[roomote]

Thanks for the version correction -- noted that this is on 3.47.3, not 3.47.0.

I've verified on current main that new_task is still listed in ALWAYS_AVAILABLE_TOOLS (src/shared/tools.ts:330), so the underlying issue is still present. The plan I proposed above would still apply to the current codebase.

Holding off on implementation per your request. Let me know when you've had a chance to verify things on your end and whether you'd like me to proceed.