mistralai/cli cli/v0.6.0

mistral CLI v0.6.0

Repository: mistralai/cli

Tag: cli/v0.6.0

Published: 2026-09-16T16:59:08Z

Prerelease: no

Release notes:

Added

• Derived capability activation: a capability can declare activatedWhen

prerequisites and installs automatically once they are all selected, deactivating when any prerequisite is removed. A derived capability cannot be removed directly — remove one of its prerequisites instead.

• mistral apps capability list runs outside an app, taking its registry from

the same flags mistral apps init uses, so the ids valid for init --caps are discoverable before an app exists. On a terminal the rows are an aligned table; down a pipe they are tab-separated with the default-branch notice on stderr.

• mistral apps capability list reports the installed version of each

capability.

• mistral apps init can report the generated scaffold as JSON.
• mistral apps dev ships a machine-wide local-development environment for the

apps gateway: the OIDC issuer defaults to the production realm, SESSION_SECRET is persisted under the config directory, and every value can be overridden from the caller environment.

• Every command that exposes machine-readable output now points at --json from

its --help.

Changed

• The fetched registry descriptor is cached under the user config directory,

keyed on its resolved coordinates (acquisition URL, package name, and version), so discovering capabilities and then scaffolding installs the index package once instead of once per command. Immutable published versions never expire; an unversioned spec or a plain descriptor URL is honoured for 15 minutes (MISTRAL_APPS_REGISTRY_CACHE_TTL, in seconds; 0 disables it); file:// descriptors are never cached.

Fixed

• Failed steps in apps init, registry add, and capability init are

reported as failures on stderr instead of a green success glyph; steps that continue regardless (bun install, uv lock) warn and name the command to run by hand.

• mistral apps dev spawns the gateway from an immutable, hash-named cache

path, so two runs in one checkout can no longer exec each other's half-written binary.