22cf2a6e91
- Promotes refreshed multi-row status area and footer as the default experience. - Stabilizes Composer row heights to prevent layout 'jitter' during typing and model turns. - Unifies active hook status and model loading indicators into a single, stable Row 1. - Refactors settings to use backward-compatible 'Hide' booleans (ui.hideStatusTips, ui.hideStatusWit). - Removes vestigial context usage bleed-through logic in minimal mode to align with global UX direction. - Relocates toast notifications to the top status row for improved visibility. - Updates all CLI UI snapshots and architectural tests to reflect the stabilized layout. - Fixes persistent TypeScript compilation errors in tests by refactoring async render helpers (`LoadingIndicator.test.tsx`, `AppHeader.test.tsx`, `ToolMessage.test.tsx`) to avoid direct destructuring of complex inferred return types, ensuring consistent Promise flattening across all CI environments (Node 20/22/24).
2.6 KiB
Gemini CLI model selection (/model command)
Select your Gemini CLI model. The /model command lets you configure the model
used by Gemini CLI, giving you more control over your results. Use Pro
models for complex tasks and reasoning, Flash models for high speed results,
or the (recommended) Auto setting to choose the best model for your tasks.
Note: The
/modelcommand (and the--modelflag) does not override the model used by sub-agents. Consequently, even when using the/modelflag you may see other models used in your model usage reports.
How to use the /model command
Use the following command in Gemini CLI:
/model
Running this command will open a dialog with your options:
| Option | Description | Models |
|---|---|---|
| Auto (Gemini 3) | Let the system choose the best Gemini 3 model for your task. | gemini-3-pro-preview, gemini-3-flash-preview |
| Auto (Gemini 2.5) | Let the system choose the best Gemini 2.5 model for your task. | gemini-2.5-pro, gemini-2.5-flash |
| Manual | Select a specific model. | Any available model. |
We recommend selecting one of the above Auto options. However, you can select Manual to select a specific model from those available.
You can also use the --model flag to specify a particular Gemini model on
startup. For more details, refer to the
configuration documentation.
Changes to these settings will be applied to all subsequent interactions with Gemini CLI.
Best practices for model selection
-
Default to Auto. For most users, the Auto option model provides a balance between speed and performance, automatically selecting the correct model based on the complexity of the task. Example: Developing a web application could include a mix of complex tasks (building architecture and scaffolding the project) and simple tasks (generating CSS).
-
Switch to Pro if you aren't getting the results you want. If you think you need your model to be a little "smarter," you can manually select Pro. Pro will provide you with the highest levels of reasoning and creativity. Example: A complex or multi-stage debugging task.
-
Switch to Flash or Flash-Lite if you need faster results. If you need a simple response quickly, Flash or Flash-Lite is the best option. Example: Converting a JSON object to a YAML string.