/mistral commands
The /mistral command family: show every effective value, write one key, or test the connection.
/mistral
Section titled “/mistral”Shows a status card: every key’s effective value with its provenance (project file, user file, env, default or unset), the auth source label (never the key value), the effective chat endpoint, the config chain with the loaded file marked, the project-scope state, any unsupported server tools, and any loader warnings. When no key is configured it prints:
Auth: not configured — run /login mistral-native or set MISTRAL_API_KEY/mistral set [--project] <key> <value>
Section titled “/mistral set [--project] <key> <value>”Writes one key. The user scope is the default; --project writes <cwd>/.pi/mistral-native.json and is refused without project trust.
/mistral set endpoint.region eu/mistral set --project agentId my-agentList-kind keys (serverTools, connectors, connectorTools.autoLoad) accept mutation syntax:
| Value | Effect |
|---|---|
+entry |
Appends the entry (deduplicated); +a,+b adds both |
-entry |
Removes the entry; a no-op with a note when absent |
| bare key | Clears the list |
| comma-separated | Replaces the list wholesale |
+/- prefixes are parsed only for list-kind keys — a string value starting with + or - is stored literally. A no-op mutation writes nothing.
Writes are atomic and merge-preserving: an existing file that is not valid JSON or fails validation is refused with an error telling you to fix the file by hand; nothing is written on refusal. After a successful write the live session picks the value up immediately; other running sessions pick it up at their next session start.
models.rateCard is not settable here (nested object) — hand-edit mistral-native.json. Unknown keys get the same Usage error, which lists all settable keys.
/mistral test
Section titled “/mistral test”Runs a live GET /models check against the effective chat endpoint. Failures name their step and carry a fix hint:
| Step | Meaning |
|---|---|
auth |
No API key available, or the key was rejected (401/403) |
network |
The endpoint could not be reached |
http |
The endpoint answered, but not with a model list |
The probe hits the same endpoint the chat stream posts to, including a gateway set through endpoint.baseUrl.
Completion
Section titled “Completion”Typing /mistral offers subcommands; the key position offers every settable key; the value position offers values per key kind — booleans (true/false), the region values (global/eu/us), and for list keys +entry and -entry hints (+ hints for serverTools include the known tool names). Tab completes at every argument position.
See Configuration keys · Change a setting · Fix a configuration error