Skills for cmux terminal integration: browser automation for visual verification, debug windows, markdown viewer, and core topology control. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1.4 KiB
1.4 KiB
Video Recording
Status and alternatives for capturing browser automation evidence in cmux.
Related: commands.md, SKILL.md
Contents
Current Status
cmux browser currently does not expose a built-in video recording command.
Why: cmux browser automation runs on WKWebView, and the agent-browser style recording pipeline is Chrome/CDP-specific.
Recommended Alternatives
1. Step Screenshots
cmux browser surface:7 screenshot > /tmp/step1.b64
cmux browser surface:7 click e3 --snapshot-after --json
cmux browser surface:7 screenshot > /tmp/step2.b64
2. Snapshot Timeline
cmux browser surface:7 snapshot --interactive > /tmp/snap-1.txt
cmux browser surface:7 click e3 --snapshot-after --json > /tmp/action-1.json
cmux browser surface:7 snapshot --interactive > /tmp/snap-2.txt
3. macOS Window Capture (external)
Use an external screen recorder if full-motion capture is required.
Use Cases
- Debug flaky browser automation.
- Produce artifacts for CI logs.
- Document flow changes between releases.
Best Practices
- Capture snapshot before and after each mutating action.
- Add
--snapshot-afteron clicks/fills/types that change state. - Keep artifacts grouped by timestamp/run id.