From 6b7fb140fdc0a3e1765083069d6a55b9f01c2d1e Mon Sep 17 00:00:00 2001 From: hannesrudolph Date: Fri, 18 Apr 2025 18:22:37 -0600 Subject: [PATCH] docs: correct terminology from 'tasks' to 'modes' in sticky models section for consistency --- docs/basic-usage/using-modes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/basic-usage/using-modes.md b/docs/basic-usage/using-modes.md index be9bcdbc..4170e42f 100644 --- a/docs/basic-usage/using-modes.md +++ b/docs/basic-usage/using-modes.md @@ -3,7 +3,7 @@ Modes in Roo Code are specialized personas that tailor the assistant's behavior to your current task. Each mode offers different capabilities, expertise, and access levels to help you accomplish specific goals. :::info Sticky Models -Each mode remembers your last-used model. When switching modes, Roo automatically selects that model—no manual selection needed. Assign different models to different tasks (Gemini 2.5 Flash thinking for architect mode, Claude Sonnet 3.7 for code mode) and Roo will switch models automatically when you change modes. +Each mode remembers your last-used model. When switching modes, Roo automatically selects that model—no manual selection needed. Assign different models to different modes (Gemini 2.5 Flash thinking for architect mode, Claude Sonnet 3.7 for code mode) and Roo will switch models automatically when you change modes. ::: ## Why Use Different Modes?