Computer History
The encrypted, metadata-only Computer History preview.
The encrypted, metadata-only Computer History preview.
| Command | Description |
|---|---|
cua-driver history enable | Turn on the Computer History preview (admits it on a local daemon if needed). |
cua-driver history disable | Turn Computer History off; recorded chunks stay until deleted. |
cua-driver history pause | Pause recording without turning the preview off. |
cua-driver history resume | Resume recording after pause. |
cua-driver history status | Print the Computer History state. |
cua-driver history flush | Seal the current chunk to disk now. |
cua-driver history list | List recent metadata-only events. |
cua-driver history show | Print one event by its sequence number. |
cua-driver history delete | Delete the encrypted chunks and their native credential-store key. |
Every command also accepts the global options.
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.
| Flag | Type | Default | Description |
|---|---|---|---|
--socket | string | Override the daemon socket or named-pipe path. | |
--json | boolean | false | Emit machine-readable output. |
Examples
# Print the Computer History state
cua-driver historycua-driver history enable#Turn on the Computer History preview (admits it on a local daemon if needed).
cua-driver history enableExamples
# Turn on the Computer History preview
cua-driver history enablecua-driver history disable#Turn Computer History off; recorded chunks stay until deleted.
cua-driver history disableExamples
# Turn Computer History off
cua-driver history disablecua-driver history pause#Pause recording without turning the preview off.
cua-driver history pauseExamples
# Pause recording
cua-driver history pausecua-driver history resume#Resume recording after pause.
cua-driver history resumeExamples
# Resume recording
cua-driver history resumecua-driver history status#Print the Computer History state. The default subcommand.
cua-driver history status [OPTIONS]| Flag | Type | Default | Description |
|---|---|---|---|
--json | boolean | false | Emit machine-readable output. |
Examples
# Print the state as JSON
cua-driver history status --jsoncua-driver history flush#Seal the current chunk to disk now.
cua-driver history flushExamples
# Seal the current chunk now
cua-driver history flushcua-driver history list#List recent metadata-only events.
cua-driver history list [OPTIONS] [<limit>]| Argument | Type | Default | Description |
|---|---|---|---|
<limit> | number | optional | Most events to print. |
| Flag | Type | Default | Description |
|---|---|---|---|
--json | boolean | false | Emit machine-readable output. |
Examples
# List the 20 most recent events
cua-driver history list 20cua-driver history show#Print one event by its sequence number.
cua-driver history show [OPTIONS] <sequence>| Argument | Type | Default | Description |
|---|---|---|---|
<sequence> | number | required | Event sequence number. |
| Flag | Type | Default | Description |
|---|---|---|---|
--json | boolean | false | Emit machine-readable output. |
Examples
# Print event 42 as JSON
cua-driver history show 42 --jsoncua-driver history delete#Delete the encrypted chunks and their native credential-store key. Needs --yes.
cua-driver history delete [OPTIONS]| Flag | Type | Default | Description |
|---|---|---|---|
--yes | boolean | false | Confirm irreversible deletion of encrypted chunks and their native credential-store key. |
Examples
# Delete every recorded chunk and its key
cua-driver history delete --yes| 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). |