Skills, recording and history

The agent skill pack, signed extensions and the perception parser; trajectory recording; the Computer History preview.

CommandDescription
cua-driver skillsInstall, update, inspect, or remove the optional agent skill pack.
cua-driver skills installFetch the versioned skill pack and link detected agents.
cua-driver skills updateRefresh the local skill pack and links.
cua-driver skills uninstallRemove agent skill links.
cua-driver skills statusReport local skill-pack and per-agent link state.
cua-driver skills pathPrint the local skill-pack path.
cua-driver extensionInspect and manage signed, target-specific optional extensions.
cua-driver extension listList registry-known extensions and local state.
cua-driver extension infoCompatibility alias for installed extension status.
cua-driver extension inspectVerify and preview license, source, provenance, and hashes without mutation.
cua-driver extension statusVerify installed integrity and optionally run the self-test hook.
cua-driver extension installVerify, stage, and durably activate an extension.
cua-driver extension updateVerify and atomically activate a newer extension version.
cua-driver extension removeRemove only a fully validated, manager-owned extension tree.
cua-driver extension pathCompatibility command that prints the exact active version directory.
cua-driver perceptionParse a local PNG with the installed optional perception extension.
cua-driver perception parseParse one local PNG into canonical visual regions.
cua-driver recordingControl trajectory recording on a running daemon.
cua-driver recording startStart trajectory recording to a directory.
cua-driver recording stopStop trajectory recording.
cua-driver recording statusPrint the current recording state.
cua-driver recording renderRender a recorded trajectory directory to an MP4.
cua-driver historyEncrypted, metadata-only Computer History early preview: lifecycle and local inspection.
cua-driver history enableTurn on the Computer History preview (admits it on a local daemon if needed).
cua-driver history disableTurn Computer History off; recorded chunks stay until deleted.
cua-driver history pausePause recording without turning the preview off.
cua-driver history resumeResume recording after pause.
cua-driver history statusPrint the Computer History state.
cua-driver history flushSeal the current chunk to disk now.
cua-driver history listList recent metadata-only events.
cua-driver history showPrint one event by its sequence number.
cua-driver history deleteDelete the encrypted chunks and their native credential-store key.

Every command also accepts the global options.

cua-driver skills#

Install, update, inspect, or remove the optional agent skill pack.

The install script never touches agent skill directories automatically.

cua-driver skills [COMMAND]

Without a subcommand, runs cua-driver skills status.

Examples

# Report skill-pack state
cua-driver skills

cua-driver skills install#

Fetch the versioned skill pack and link detected agents.

cua-driver skills install [OPTIONS]
FlagTypeDefaultDescription
--fromstringFetch from the main branch instead of the tagged release. Only main is accepted; write it as --from=main.
--all-platformsbooleanfalseKeep platform-specific skill files for every platform.
--forcebooleanfalseRe-fetch the skill pack even when the local copy is current.

Examples

# Install the skill pack and link detected agents
cua-driver skills install
 
# Install the latest skill pack from main
cua-driver skills install --from=main

cua-driver skills update#

Refresh the local skill pack and links.

Always re-fetches; takes the same options as install.

cua-driver skills update [OPTIONS]
FlagTypeDefaultDescription
--fromstringFetch from the main branch instead of the tagged release. Only main is accepted; write it as --from=main.
--all-platformsbooleanfalseKeep platform-specific skill files for every platform.

Examples

# Refresh the skill pack and links
cua-driver skills update

cua-driver skills uninstall#

Remove agent skill links.

cua-driver skills uninstall [OPTIONS]
FlagTypeDefaultDescription
--allbooleanfalseAlso delete the local skill-pack copy.

Examples

# Remove the links and the local copy
cua-driver skills uninstall --all

cua-driver skills status#

Report local skill-pack and per-agent link state.

cua-driver skills status

Examples

# Report skill-pack and link state
cua-driver skills status

cua-driver skills path#

Print the local skill-pack path.

cua-driver skills path

Examples

# Print the skill-pack path
cua-driver skills path

cua-driver extension#

Inspect and manage signed, target-specific optional extensions.

Verified installs bind a pinned publisher identity and Ed25519 key validity/rotation state to exact catalog, archive, manifest, file, original-model, and converted-model hashes plus component licenses/notices and corresponding-source revisions. Inspect previews license, source, and provenance before mutation. Explicit developer-only unsigned installs remain visibly unverified. Install, update, and remove use platform-specific ownership and link/reparse-point checks on macOS, Linux, and Windows.

cua-driver extension [COMMAND]

Without a subcommand, runs cua-driver extension list.

Examples

# List known extensions
cua-driver extension list

cua-driver extension list#

List registry-known extensions and local state.

cua-driver extension list [OPTIONS]
FlagTypeDefaultDescription
--jsonbooleanfalseEmit machine-readable output.

Examples

# List extensions as JSON
cua-driver extension list --json

cua-driver extension info#

Compatibility alias for installed extension status.

cua-driver extension info [OPTIONS] <name>
ArgumentTypeDefaultDescription
<name>stringrequiredRegistry extension name.
FlagTypeDefaultDescription
--jsonbooleanfalseEmit machine-readable output.

Examples

# Show an installed extension
cua-driver extension info cua-perception

cua-driver extension inspect#

Verify and preview license, source, provenance, and hashes without mutation.

cua-driver extension inspect [OPTIONS] <name>
ArgumentTypeDefaultDescription
<name>stringrequiredRegistry extension name.
FlagTypeDefaultDescription
--catalogpathSigned local catalog.
--archivepathDeveloper-only unsigned local archive.
--allow-unsigned-localbooleanfalseExplicitly select developer-only unverified mode.
--jsonbooleanfalseEmit machine-readable output.

Examples

# Preview license, source and provenance
cua-driver extension inspect cua-perception --catalog catalog.json

cua-driver extension status#

Verify installed integrity and optionally run the self-test hook.

cua-driver extension status [OPTIONS] [<name>]
ArgumentTypeDefaultDescription
<name>stringoptionalOptional registry extension name.
FlagTypeDefaultDescription
--self-testbooleanfalseRun the extension self-test hook.
--jsonbooleanfalseEmit machine-readable output.

Examples

# Verify an extension and run its self-test
cua-driver extension status cua-perception --self-test

cua-driver extension install#

Verify, stage, and durably activate an extension.

Supported on macOS, Linux, and Windows with platform ownership and link/reparse-point checks.

cua-driver extension install [OPTIONS] <name>
ArgumentTypeDefaultDescription
<name>stringrequiredRegistry extension name.
FlagTypeDefaultDescription
--catalogpathSigned local catalog.
--archivepathDeveloper-only unsigned local archive.
--allow-unsigned-localbooleanfalseExplicitly select developer-only unverified mode.

Examples

# Install from a signed catalog
cua-driver extension install cua-perception --catalog catalog.json

cua-driver extension update#

Verify and atomically activate a newer extension version.

Supported on macOS, Linux, and Windows with platform ownership and link/reparse-point checks.

cua-driver extension update [OPTIONS] <name>
ArgumentTypeDefaultDescription
<name>stringrequiredRegistry extension name.
FlagTypeDefaultDescription
--catalogpathSigned local catalog.
--archivepathDeveloper-only unsigned local archive.
--allow-unsigned-localbooleanfalseExplicitly select developer-only unverified mode.

Examples

# Activate a newer version
cua-driver extension update cua-perception --catalog catalog.json

cua-driver extension remove#

Remove only a fully validated, manager-owned extension tree.

Supported on macOS, Linux, and Windows with platform ownership and link/reparse-point checks.

cua-driver extension remove <name>
ArgumentTypeDefaultDescription
<name>stringrequiredRegistry extension name.

Examples

# Remove an extension
cua-driver extension remove cua-perception

cua-driver extension path#

Compatibility command that prints the exact active version directory.

cua-driver extension path <name>
ArgumentTypeDefaultDescription
<name>stringrequiredRegistry extension name.

Examples

# Print the active version directory
cua-driver extension path cua-perception

cua-driver perception#

Parse a local PNG with the installed optional perception extension.

This read-only local-input mode does not create a Driver capture. Its visual-regions JSON marks the result ineligible for Driver action authority.

cua-driver perception <COMMAND>

Examples

# Parse a PNG into visual regions
cua-driver perception parse --image screen.png --capture capture.json --json

cua-driver perception parse#

Parse one local PNG into canonical visual regions.

Requires --json. The capture file supplies source metadata only.

cua-driver perception parse [OPTIONS]
FlagTypeDefaultDescription
--imagepathrequiredLocal PNG path.
--capturepathrequiredLocal capture source metadata JSON path.
--jsonbooleanfalseEmit canonical visual-regions JSON with local-input provenance.

Examples

# Parse a PNG into visual regions
cua-driver perception parse --image screen.png --capture capture.json --json

cua-driver recording#

Control trajectory recording on a running daemon.

Recording state lives in the required daemon and survives client reconnects.

cua-driver recording [OPTIONS] [COMMAND]

Without a subcommand, runs cua-driver recording status.

FlagTypeDefaultDescription
--socketstringOverride the daemon socket or named-pipe path.

Examples

# Print the current recording state
cua-driver recording

cua-driver recording start#

Start trajectory recording to a directory.

cua-driver recording start <output-dir>
ArgumentTypeDefaultDescription
<output-dir>pathrequiredDirectory to write turn folders into.

Examples

# Record turns into a directory
cua-driver recording start ~/cua-trajectories/demo1

cua-driver recording stop#

Stop trajectory recording.

cua-driver recording stop

Examples

# Stop recording
cua-driver recording stop

cua-driver recording status#

Print the current recording state.

cua-driver recording status

Examples

# Print the recording state
cua-driver recording status

cua-driver recording render#

Render a recorded trajectory directory to an MP4.

This pure file-to-file path does not require a running daemon.

cua-driver recording render [OPTIONS] <input-dir> <out-mp4>
ArgumentTypeDefaultDescription
<input-dir>pathrequiredTrajectory directory containing recorded turn folders.
<out-mp4>pathrequiredOutput MP4 path.
FlagTypeDefaultDescription
--scalenumberScale factor for rendered frames.
--no-zoombooleanfalseDisable cursor/action zoom effects in the rendered video.

Examples

# Render a recorded trajectory to MP4
cua-driver recording render ~/cua-trajectories/demo1 demo1.mp4

cua-driver history#

Encrypted, metadata-only Computer History early preview: lifecycle and local inspection.

The daemon must be admitted for the preview (cua-driver serve --experimental-history); enable restarts a local daemon with it when needed.

cua-driver history [OPTIONS] [COMMAND]

Without a subcommand, runs cua-driver history status.

FlagTypeDefaultDescription
--socketstringOverride the daemon socket or named-pipe path.
--jsonbooleanfalseEmit machine-readable output.

Examples

# Print the Computer History state
cua-driver history

cua-driver history enable#

Turn on the Computer History preview (admits it on a local daemon if needed).

cua-driver history enable

Examples

# Turn on the Computer History preview
cua-driver history enable

cua-driver history disable#

Turn Computer History off; recorded chunks stay until deleted.

cua-driver history disable

Examples

# Turn Computer History off
cua-driver history disable

cua-driver history pause#

Pause recording without turning the preview off.

cua-driver history pause

Examples

# Pause recording
cua-driver history pause

cua-driver history resume#

Resume recording after pause.

cua-driver history resume

Examples

# Resume recording
cua-driver history resume

cua-driver history status#

Print the Computer History state. The default subcommand.

cua-driver history status [OPTIONS]
FlagTypeDefaultDescription
--jsonbooleanfalseEmit machine-readable output.

Examples

# Print the state as JSON
cua-driver history status --json

cua-driver history flush#

Seal the current chunk to disk now.

cua-driver history flush

Examples

# Seal the current chunk now
cua-driver history flush

cua-driver history list#

List recent metadata-only events.

cua-driver history list [OPTIONS] [<limit>]
ArgumentTypeDefaultDescription
<limit>numberoptionalMost events to print.
FlagTypeDefaultDescription
--jsonbooleanfalseEmit machine-readable output.

Examples

# List the 20 most recent events
cua-driver history list 20

cua-driver history show#

Print one event by its sequence number.

cua-driver history show [OPTIONS] <sequence>
ArgumentTypeDefaultDescription
<sequence>numberrequiredEvent sequence number.
FlagTypeDefaultDescription
--jsonbooleanfalseEmit machine-readable output.

Examples

# Print event 42 as JSON
cua-driver history show 42 --json

cua-driver history delete#

Delete the encrypted chunks and their native credential-store key. Needs --yes.

cua-driver history delete [OPTIONS]
FlagTypeDefaultDescription
--yesbooleanfalseConfirm irreversible deletion of encrypted chunks and their native credential-store key.

Examples

# Delete every recorded chunk and its key
cua-driver history delete --yes

Exit codes#

CodeMeaning
0Success.
1Failure: 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.
2Invalid input: tool arguments that are not valid JSON, an unknown mcp-config client, or an update --apply refused on a local development install.
64Usage 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).