eval/skills/record/SKILL.md
Record terminal sessions (asciinema) or desktop video (pixelflux/wf-recorder). MUST be invoked before any work involving: ov eval record commands, terminal recording, desktop video recording, or session capture.
npx skillsauth add overthinkos/overthink-plugins recordInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
ov eval record manages recording sessions inside running containers. It is one
of the live-container verbs under ov eval (see /ov-eval:eval for the full
family: cdp/wl/dbus/vnc/mcp/spice/libvirt/record). It supports two modes:
.cast filesAll recording sessions are managed via tmux sessions with a record- prefix. This provides background execution, output monitoring, and clean start/stop lifecycle.
| Action | Command | Description |
|--------|---------|-------------|
| Start recording | ov eval record start <image> [-n NAME] [-m MODE] | Start a recording session |
| Stop recording | ov eval record stop <image> [-n NAME] [-o FILE] | Stop and optionally copy to host |
| List recordings | ov eval record list <image> | Show active recording sessions |
| Send command | ov eval record cmd <image> "command" [-n NAME] | Send command to recording terminal |
ov eval record start — Start Recordingov eval record start <image> [--name NAME] [--mode MODE] [--fps FPS] [--audio] [-i INSTANCE]
Flags:
-n, --name — Recording name (default: default). Multiple concurrent recordings supported-m, --mode — terminal (asciinema), desktop (video), or auto (auto-detect)--fps — Frames per second for desktop recording (default: 30)--audio — Include PulseAudio audio capture (desktop mode)Auto-detection order: pixelflux-record → wf-recorder → asciinema
Output files (inside container):
/tmp/ov-recordings/<name>.cast/tmp/ov-recordings/<name>.mp4ov eval record stop — Stop Recordingov eval record stop <image> [--name NAME] [--output FILE] [-i INSTANCE]
-o, --output copies the recording file from the container to the hostov eval record list — List Active Recordingsov eval record list <image> [-i INSTANCE]
Shows all active recording sessions with name, mode, and file path.
ov eval record cmd — Send Command to Recordingov eval record cmd <image> "command" [--name NAME] [-i INSTANCE]
Sends a command to the recording's tmux session. For terminal recordings, the command and its output become part of the .cast file. Convenience wrapper for ov tmux send <image> -s record-<name> "command" --enter. Sends a desktop notification when the command is dispatched (if a notification daemon like swaync is running).
| Tool | Layer | Desktop | Protocol |
|------|-------|---------|----------|
| asciinema | asciinema (or dev-tools) | N/A | Terminal capture |
| pixelflux-record | wl-record-pixelflux | selkies-desktop | selkies WebSocket capture bridge → H.264 → ffmpeg |
| wf-recorder | wf-recorder | sway-desktop | wlr-screencopy |
# Start recording
ov eval record start openclaw -n demo --mode terminal
# Run commands (each appears in the recording)
ov eval record cmd openclaw "echo 'Hello World'" -n demo
ov eval record cmd openclaw "ls -la" -n demo
ov eval record cmd openclaw "ov --help" -n demo
# Or attach interactively
ov tmux attach openclaw -s record-demo
# ... interact, Ctrl-b d to detach
# Stop and save
ov eval record stop openclaw -n demo -o demo.cast
# Play back locally
asciinema play demo.cast
# Start desktop video recording with audio
ov eval record start selkies-desktop -n walkthrough --mode desktop --audio
# Run CLI commands (visible in recording)
ov eval record cmd selkies-desktop "git status" -n walkthrough
ov eval record cmd selkies-desktop "docker ps" -n walkthrough
# Interact with browser
ov eval cdp open selkies-desktop "https://github.com"
ov eval wl click selkies-desktop 640 360
# Stop and save
ov eval record stop selkies-desktop -n walkthrough -o walkthrough.mp4
asciinema layer (or dev-tools)wl-record-pixelflux layer (included in selkies-desktop metalayer)wf-recorder layer (included in sway-desktop metalayer)tmux layer must be present (for session management)ov eval record cmd uses the shared sendTmuxCommand() helper (also used by ov tmux cmd)sendContainerNotification() on every ov eval record cmd dispatch (always-on, no --no-notify flag — recording context always benefits from notification)sendContainerNotification() → tries in-container ov eval dbus notify . → falls back to gdbus call → silently skips if neither available/ov-automation:tmux — Underlying tmux session management (recording sessions use record- prefix). ov tmux cmd uses the same sendTmuxCommand helper/ov-coder:asciinema — Terminal recording layer/ov-selkies:wl-record-pixelflux — Pixelflux video recording layer/ov-selkies:wf-recorder — wf-recorder video recording layer/ov-selkies:selkies-desktop-layer — Desktop metalayer with pixelflux recording/ov-selkies:sway-desktop — Desktop metalayer with wf-recorder/ov-infrastructure:dbus-layer — D-Bus session bus (required for notification delivery)/ov-selkies:swaync — Notification daemon (displays the notifications)/ov-eval:wl — Desktop automation (used alongside recording)/ov-eval:wl-overlay — Fullscreen overlays (title cards, lower-thirds, fades — compose with recording workflow)/ov-eval:cdp — Chrome automation (used alongside recording)MUST be invoked when the task involves:
ov eval record commandsdevelopment
Claude Code multi-agent support in Overthink — sub-agents, dynamic workflows, and agent teams, and how each drives the existing `ov eval` disposable beds to test and verify. MUST be invoked before authoring or invoking an ov sub-agent / dynamic workflow / agent team, wiring agent-lifecycle hooks, or asking "which primitive should drive the R10 beds?".
tools
Mounts a virtiofs share tagged `workspace` at /workspace inside a VM guest via a systemd .mount unit. Use when a kind:vm entity shares a host directory into the guest and you need it auto-mounted (and re-mounted at every boot).
development
MUST be invoked before any work involving: the `kind: android` schema kind, a `target: android` deploy, the `apk:` layer package format (installing Android apps declaratively), AndroidDeployTarget, an in-pod emulator OR a remote/physical adb-endpoint device, or nested `pod → android` deployment. The first-class Android device + app surface that sits above `ov eval adb`/`appium`.
tools
Use when committing, branching, pushing, merging, tagging, creating PRs, or approving/merging PRs with gh — the feat/-branch, R10-gated, never-force-push landing workflow across the main repo + the plugins submodule + image/<distro> submodules. Covers sync-to-upstream, branch/worktree pruning, the fork+PR path for contributors without write access, and cross-repo @github landing order.