Updates
Check for and apply updates, and choose the release channel.
Check for and apply updates, and choose the release channel.
| Command | Description |
|---|---|
cua-driver check-update | Check whether a newer cua-driver release is available. |
cua-driver update | Check for an update and optionally apply it. |
cua-driver channel | Inspect or change the stable/nightly update channel. |
cua-driver channel status | Show selected and current release channels. |
cua-driver channel set | Save stable or nightly as the update channel. |
Every command also accepts the global options.
cua-driver check-update#Check whether a newer cua-driver release is available.
Read-only. Uses the same update-state payload as the check_for_update MCP tool.
cua-driver check-update [OPTIONS]| Flag | Type | Default | Description |
|---|---|---|---|
--json | boolean | false | Emit a machine-readable JSON payload. |
--no-cache | boolean | false | Skip the 20-hour on-disk cache and force a GitHub request. |
Examples
# Check for a newer release
cua-driver check-update
# Check now, as JSON
cua-driver check-update --json --no-cachecua-driver update#Check for an update and optionally apply it.
The apply path delegates to the canonical platform installer scripts.
cua-driver update [OPTIONS]| Flag | Type | Default | Description |
|---|---|---|---|
--apply | boolean | false | Download and install the latest release when one is available. |
--json | boolean | false | Emit the structured update-state payload. |
Examples
# Check and print the install command
cua-driver update
# Install the latest release
cua-driver update --applycua-driver channel#Inspect or change the stable/nightly update channel.
Selection is persistent but never installs by itself; use cua-driver update --apply after changing it.
cua-driver channel [COMMAND]Without a subcommand, runs cua-driver channel status.
Examples
# Show the selected release channel
cua-driver channelcua-driver channel status#Show selected and current release channels.
cua-driver channel status [OPTIONS]| Flag | Type | Default | Description |
|---|---|---|---|
--json | boolean | false | Emit machine-readable channel state. |
Examples
# Show the channels as JSON
cua-driver channel status --jsoncua-driver channel set#Save stable or nightly as the update channel.
cua-driver channel set [OPTIONS] <channel>| Argument | Type | Default | Description |
|---|---|---|---|
<channel> | string | required | Release channel: stable or nightly. |
| Flag | Type | Default | Description |
|---|---|---|---|
--json | boolean | false | Emit machine-readable channel state. |
Examples
# Follow nightly builds (then run update --apply)
cua-driver channel set nightly| Code | Meaning |
|---|---|
0 | Success. |
1 | Failure: the daemon is not running or is incompatible, a tool call returned an error, or the operation failed. call and direct tool invocations exit with the daemon's result code (1 on a tool error); update --apply passes through the installer's status. |
2 | Invalid input: tool arguments that are not valid JSON, an unknown mcp-config client, or an update --apply refused on a local development install. |
64 | Usage error: an unknown or missing subcommand or argument, or conflicting flags (for example revoke without exactly one of --session or --all, or an authorization flag passed to mcp). |