Back to rankings

Mistral Vibe: Redesigned /config Settings Browser

Mistral VibeView original changelog

Mistral Vibe v2.23.2 redesigned the /config command into a searchable, full-screen settings browser with typed edit modals and a per-layer origin display, replacing the older flat configuration menu. The overhaul makes it possible to search across every available setting, edit values through validated input fields instead of raw TOML, and see exactly which layer, CLI flag, environment variable, or project file, set each active value. The redesign follows on from July's migration to ConfigOrchestrator, which moved default values out of config.toml so the file only stores settings a user has explicitly changed.

Key Takeaways

  • Mistral Vibe redesigned /config into a searchable, full-screen settings browser with typed edit modals, replacing the older flat configuration menu.
  • The new interface shows a per-layer origin display, so users can see exactly which layer, CLI flag, environment variable, or project file, set each active value.
  • The redesign follows July's migration to ConfigOrchestrator, which moved default values out of config.toml so the file only stores settings a user explicitly changed.
  • Typed edit modals validate input as users change settings, reducing the chance of malformed config.toml entries that previously required manual TOML editing.
  • The change makes Mistral Vibe's growing list of configuration options — models, hooks, ACP settings, and more — easier to discover without reading documentation.
  • The redesign shipped alongside a fix for a related bug where extra fields in the whoami response were incorrectly rejected, hardening the configuration and auth pipeline together.

A Full-Screen, Searchable /config

Mistral Vibe v2.23.2, released July 30, 2026, redesigned the /config command from a simple menu into a searchable, full-screen settings browser. The new interface adds typed edit modals for changing individual values and a per-layer origin display that shows exactly where each active setting comes from.

Why the Redesign Matters

Mistral Vibe's configuration surface has grown steadily: provider settings, model aliases, hooks, ACP options, telemetry, and more, all layer together from global config, project-level .vibe/config.toml, environment variables, and command-line flags. Finding and changing a specific setting previously meant knowing where to look, and often meant editing TOML by hand. The redesigned /config turns that into a searchable browsing experience, letting users type a setting name and jump straight to it, then edit it through a typed modal that validates input rather than accepting free-form text.

The per-layer origin display is a particularly practical addition: when a value doesn't seem to be taking effect, users can now see immediately whether it's set by a CLI flag, an environment variable, the project config, or the global config, and at what priority it's being applied. This directly addresses a common source of configuration confusion in layered config systems.

Building on Recent Config Infrastructure Work

This user-facing redesign follows several releases of underlying groundwork. The July 21 release (v2.22.0) completed a full migration to ConfigOrchestrator for configuration handling and moved default values to a DefaultConfigLayer, so config.toml on disk stores only settings a user has explicitly changed rather than every default value. The July 17 release (v2.21.0) exposed the config schema through ACP. The new /config browser is the visible payoff of that infrastructure work, giving users a properly structured, typed interface on top of it.

Related Fixes

The same release fixed a bug where extra fields in the whoami response were incorrectly rejected, hardening the configuration and authentication pipeline alongside the UI overhaul.