mistralai/cli cli/v0.11.0

mistral CLI v0.11.0

Repository: mistralai/cli

Tag: cli/v0.11.0

Published: 2026-10-23T14:54:13Z

Prerelease: no

Release notes:

Breaking

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

mistral apps registry add, update and remove no longer take --dry-run. Except for registry remove, which just removes, they still print their plan and ask for confirmation as before; declining leaves the app unchanged.

• mistral apps publish and mistral apps unpublish no longer take

--dry-run, so their --json outcome is never would_publish or would_unpublish.

• mistral apps init, mistral apps capability add, and a git

mistral apps registry update end with a # Install document instead of the "Before you run" section: the list items (and any paragraph) under each ## heading of the new capabilities' INSTALL.md files, merged by heading (all their ## Prerequisites in one list, a shared bullet listed once). It no longer lists the empty .env values or the path of each INSTALL.md. Under --json, the prerequisites array is replaced by install, one { title, entries } entry per merged section. An update lists the capabilities it adds in full and, for those it keeps, only the items they gained or reworded.

Added

• mistral apps deploy deploys apps with managed capabilities, from git

(commit .mistral/managed/) or --from-disk (which uploads it). It warns when a managed capability's folder is missing, edited or not committed.

• Without mistral login, mistral apps registry add --source managed,

capability add and install read a managed registry with MISTRAL_API_KEY, so CI can install managed capabilities. The key must belong to the app's deployment workspace. Managed registries still need a feature flag.

• mistral workflows init scaffolds a Mistral workflows app. It is the same

as mistral init --preset workflow, and takes the same flags except --caps, --preset, --tags and --from.

• On a terminal, mistral init first asks what you are building: Workflow

selects the same capabilities as mistral workflows init, App the registry's defaults, and Custom opens the capability pickers as before. --preset workflow or --preset app makes the same choice without asking, and cannot be combined with --caps. --yes on its own still takes the registry's defaults.

Changed

• Apps commit .mistral/managed/ for now: mistral apps install and

mistral apps capability add no longer add it to .gitignore, and remove the /.mistral/managed/ line an earlier version added.

• mistral apps install refuses a managed version disabled in the registry,

even when it is already restored or cached. Offline or signed out, it warns and restores from the cache. Managed registries still need a feature flag.

• mistral apps capability add registry/kind/id for a registry the app does

not configure now says so, and how to add it with mistral apps registry add.

• An edited CHANGELOG entry is reported whole: a nested item with its parent

entry, an indented paragraph past a blank line with its entry, and a line of a paragraph with the paragraph. A nested item under ### Breaking is no longer listed as a breaking change of its own.

Fixed

• mistral apps pins the @mistral npm scope to Mistral's internal feed in

each app's bunfig.toml, and blocks it otherwise, so @mistral/* packages never come from public npm.

• When a registry's descriptor cache (.mistral/cache//registry.json)

was never committed, or was deleted, every mistral apps command that reads the app's registries restores it at the exact version the app records instead of failing with no registry descriptor found, offline when that version is in the CLI's own cache. A registry that records no exact version is not fetched: the command says to run mistral apps registry update , which plans it against the version it moves to, with a warning, as it does a registry it updates whose recorded version can no longer be fetched.