Trajectory recording

Record, inspect and render action trajectories.

Command	Description
`cua-driver recording start`	Start trajectory recording to a directory.
`cua-driver recording stop`	Stop trajectory recording.
`cua-driver recording status`	Print the current recording state.
`cua-driver recording render`	Render a recorded trajectory directory to an MP4.

Every command also accepts the global options.

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.

Flag	Type	Default	Description
`--socket`	string		Override 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>

Argument	Type	Default	Description
`<output-dir>`	path	required	Directory to write turn folders into.

Examples

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

Stop trajectory recording.

cua-driver recording stop

Examples

# Stop recording
cua-driver recording stop

Print the current recording state.

cua-driver recording status

Examples

# Print the recording state
cua-driver recording status

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>

Argument	Type	Default	Description
`<input-dir>`	path	required	Trajectory directory containing recorded turn folders.
`<out-mp4>`	path	required	Output MP4 path.

Flag	Type	Default	Description
`--scale`	number		Scale factor for rendered frames.
`--no-zoom`	boolean	`false`	Disable cursor/action zoom effects in the rendered video.

Examples

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

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`).