The binaries no longer load .env or bunfig.toml from the working directory. Export MISTRAL_API_KEY or set apiKey in your config instead. mistral apps dev still passes the app's .env to its modules.
Added
mistral apps init uses the public capability registry on npm by default, with no token. Pass --registry-url for a private registry.
mistral apps init --caps fills a kind that only one capability can fill, so --caps workflows also adds apps.
mistral apps deploy deploys workflow workers as managed workflow deployments.
mistral apps deploy names the organization and workspace before creating anything, and ends with the app URL and a Studio link.
mistral apps deploy runs with MISTRAL_API_KEY when there is no mistral login session, for CI.
mistral apps dev starts a local Postgres in Docker for an app's managed database.
Capabilities can declare pre-start commands, such as migrations, which mistral apps dev runs before starting the module.
apps.json modules take a routes list. A route marked mcp turns on MCP client sign-in in apps dev and on deploy. routePrefix is migrated automatically.
mistral apps dev opens the app in the browser once it is ready.
The installer offers to add ~/.mistral/bin to your PATH and explains how to turn on shell completions.
mistral apps commands send usage telemetry. Set MISTRAL_TELEMETRY_OPT_OUT=1 or DO_NOT_TRACK=1 to turn it off.
Changed
mistral apps dev, config, capability, registry and modules no longer need a feature flag. deploy, publish and unpublish still do.
mistral apps deploy deploys every module at once. A failed module no longer stops the others, and the command fails at the end naming each one.
The first mistral apps deploy commits and pushes the apps.json change it makes. It asks first on a terminal, and needs --yes otherwise.
mistral apps dev calls the Mistral API as the organization and workspace from mistral login, and only falls back to MISTRAL_API_KEY without one.