Back to rankings

Mistral Vibe: Model Catalog Aliases Work Everywhere and Replace the Built-in Default

Mistral VibeView original changelog

With the model catalog enabled, a model's old name (catalog alias) now works wherever a model is named, including [models.<old name>] settings, --model and the ACP model option. The pickers show one row per catalog model and the built-in default is no longer available, with the catalog's recommended model as default.

Key Takeaways

  • Catalog aliases work in settings, --model and the ACP model option.
  • The built-in default model is unavailable when the catalog lists models.
  • The catalog's recommended model becomes the default.
  • Pickers show one row per catalog model.
  • allowed_models patterns also match aliases.
  • active_model is saved under the existing config name for older-version compatibility.

Old names keep working

Aliases work in [models.<old name>] settings, --model <old name> and the ACP model option. allowed_models patterns also match catalog aliases, so a pattern like mistral-vibe-cli-* keeps matching the catalog model that replaces it.

Catalog replaces the built-in default

When the catalog is on for the account and lists at least one model, the built-in default is not available. The pickers show one row per catalog model, no duplicate copy, and the catalog's recommended model is the default. An alias can take the built-in's name: a pin on mistral-medium-3.5 runs the catalog's mistral-medium-latest when the catalog lists that alias.

Compatibility

A model pick saves active_model under the name the config already uses, so older versions sharing the file still resolve it.

Mistral Vibe Model Catalog Aliases and New Default | Yet Another Changelog