Model Selection
Choose which AI model powers your Tabnine CLI interactions.
Opening the Model Dialog
/modelThis opens an interactive dialog showing available models.
Available Models
Tabnine CLI uses the same models described on the AI Models page.
Changing Models
Via /model Command
Open the model dialog
Run:
/modelThis opens the interactive model selection dialog.
Navigate
Use the arrow keys or J / K to move through available models.
Select
Press Enter to select the highlighted model.
Immediate effect
Model changes take effect immediately after selection.
Via /model set (Non-Interactive)
You can also change the model without opening the dialog:
/model set <model-name>This sets the model for the current session only. To persist the change across sessions, add the --persist flag:
/model set <model-name> --persistVia --model Flag
Specify the model when launching Tabnine CLI:
The -m short form also works:
Via Environment Variable
Set the TABNINE_MODEL environment variable before launching:
Model Selection Precedence
When multiple sources specify a model, the following precedence applies (highest to lowest):
--modelcommand-line flag (or-m)TABNINE_MODELenvironment variablemodel.nameinsettings.jsonDefault model from Tabnine service
Model Information
View current session statistics (including token usage):
View current model and context usage in the footer (shown if enabled in settings).
Token Limits
Tabnine CLI automatically manages token limits based on the selected model.
Fallback Behavior
If your selected model is unavailable, Tabnine CLI may:
Prompt you to select another model
Automatically fall back to a default model (depending on settings)
Model Persistence
Your model selection is saved and persists across sessions when using:
/model set <model-name> --persist— writesmodel.nametosettings.jsonThe interactive
/modeldialog — persists your selection automatically
Persistent selections are stored in .tabnine/agent/settings.json.
Fast Model Configuration
You can configure a lightweight model to handle background CLI tasks, reducing latency for operations the user never directly sees. To configure a fast model, add "fastModel": "<model-name>" to your settings.json or use the /model fast slash command in the CLI.
The following tasks are routed to the fast model when one is configured:
Session summary
Shell output summary
Tool output summary
Edit corrector
Fast ack helper
Loop detection (primary pass)
LLM edit fixer
Loop detection double-check and next-speaker checker remain on the main model, as they require higher-confidence reasoning. When no fast model is configured, all tasks use the main model. The fast model setting is provider-agnostic and works with any model the backend supports.
Last updated
Was this helpful?
