ReleaseMistral AIMistral AIpublished Oct 26, 2026seen 11h

mistralai/cli cli/v0.13.0

mistralai/cli

Open original ↗

Captured source

source ↗
published Oct 26, 2026seen 11hcaptured 11hhttp 200method plain

mistral CLI v0.13.0

Repository: mistralai/cli

Tag: cli/v0.13.0

Published: 2026-10-26T18:25:24Z

Prerelease: no

Release notes:

Added

  • mistral apps deploy warns about each server module that has no value for

an env var the app's capabilities declare with an empty default, such as MISTRAL_API_KEY, and says to set it in the app's Secrets tab in Studio. The --json report lists them under unsetEnv.

Changed

  • mistral apps init on a terminal opens the capability pickers straight away

instead of asking what you are building. mistral init still asks, and --preset, --caps, --yes and --json work the same on both.

  • init, apps init and workflows init record which of them ran

(entrypoint) and how the capabilities were chosen (selection) in their telemetry.

Fixed

  • mistral apps capability add, update, remove, mistral apps install and

mistral apps registry commands refuse a symlink committed under .mistral/ (the managed trees, the registry caches, registries.json, capabilities.json) instead of writing or deleting through it, outside the app. This covers managed, npm and git registries.

  • After installing or mistral upgrade, the next steps suggest mistral init

to scaffold a workflow or an app, instead of mistral apps init.

  • On macOS, the sign-in is stored in the keychain through /usr/bin/security,

like the GitHub CLI, so macOS should not ask for keychain access again after an update. macOS may ask once or twice after upgrading, since the existing item only trusts the previous binary. Any process running as you can read the item. The fallback file's config directory is created or tightened to 0700 when the CLI writes the fallback file, and the 0600 file used where no keychain exists still warns.

  • mistral apps deploy stops before building when GitHub has revoked the

GitHub connection, for example after a single sign-on re-authorisation, and prints the link to connect it again, as it does when GitHub is not connected. Every build used to fail instead, with nothing pointing at the connection.