Documentation
EspañolErrors and exit codes
Interpret CLI failures and recover without modifying Mico storage.
Without --json, CLI errors are written to standard error as human-readable text beginning with error:. With --json, errors are also written to standard error, as JSON with schema_version and an error object containing code, message, and exit_code.
| Exit code | Meaning | Recovery |
|---|---|---|
0 | Success | Consume stdout. |
1 | Database or operation failure, or an unhealthy doctor report | Read the reported action. For doctor, inspect the JSON report and confirm app and CLI compatibility. |
2 | Meeting, note, or other requested data not found | List meetings again and use a returned ID. |
3 | Database file not found | Open Mico once to create it, or provide the correct database path. |
4 | Export output already exists | Choose another path or explicitly pass --force to replace the file. |
64 | Invalid arguments (invalid_arguments) | Run the command with --help and fix the arguments. |
The remote MCP server reports a meeting that does not exist, or is not yours, as a tool result with isError: true, not as a protocol error. A failure while reading data is reported the same way. See the MCP reference for its protocol and HTTP errors.
Do not recover by creating tables, running migrations, or issuing SQL. The desktop app owns schema initialization and migrations.