Video Recording

Capture browser automation as video for debugging, documentation, or verification.

Related: commands.md for full command reference, SKILL.md for quick start.

Contents

• Requirements
• Basic Recording
• Recording Commands
• Frame Rate
• Visible Cursor
• Contact Sheets
• Use Cases
• Best Practices
• Output Format
• Limitations

Requirements

Recording pipes frames into ffmpeg, which must be on PATH with the libvpx and libx264 encoders. Install it with brew install ffmpeg (macOS) or sudo apt install ffmpeg (Debian/Ubuntu); agent-browser doctor reports it under "Recording". Nothing else in agent-browser needs ffmpeg.

Supported formats are .webm (VP8 via libvpx) and .mp4 (H.264 via libx264). Other extensions are handed to ffmpeg as-is with H.264 video. A path with no extension is rejected before recording starts.

Basic Recording

record start records the current active page as-is. Without a URL it attaches to the tab you already have open (no navigation, no new tab, page state and hydration intact). With a URL it navigates the active tab there first.

# Launch the browser, then start recording
agent-browser open https://example.com
agent-browser record start ./demo.webm

# Perform actions
agent-browser snapshot -i
agent-browser click @e1
agent-browser fill @e2 "test input"

# Stop and save
agent-browser record stop

Recording Commands

# Launch a session first
agent-browser open

# Start recording to file (30 fps)
agent-browser record start ./output.webm

# Start recording at a specific rate (1-60)
agent-browser record start ./output.webm --fps 60

# Stop current recording
agent-browser record stop

# Restart with new file (stops current + starts new)
agent-browser record restart ./take2.webm --fps 60

# Navigate the active tab, then record
agent-browser record start ./output.webm https://example.com/checkout

# Record in a separate tab: open it first, then start recording
agent-browser tab new https://example.com
agent-browser record start ./output.webm

Frame Rate

Recording captures 30 fps by default, so scrolling, hover states, and CSS transitions read as motion instead of a slideshow. --fps takes any rate from 1 to 60.

# Animation review
agent-browser record start ./transition.webm --fps 60
agent-browser click @e1
agent-browser wait 1500
agent-browser record stop

# Hour-long soak run
agent-browser record start ./soak.webm --fps 5

The video uses the requested frame rate and holds the latest Chrome frame between repaints. record stop --json reports frames (written) and capturedFrames (distinct frames from Chrome).

Visible Cursor

Chrome's screencast does not include the native pointer. Pass --cursor to add an animated pointer and click ripple rendered with the page, keeping drags synchronized in every captured frame. The temporary overlay is inert, hidden from accessibility snapshots, and removed when recording stops. Screenshots taken during the recording include it.

agent-browser record start ./walkthrough.webm --cursor

Contact Sheets

Pass --contact-sheet to create a timestamped summary with highlighted changes.

agent-browser record start ./checkout.webm --contact-sheet

# Select frames when at least 2% of the image changes
agent-browser record start ./checkout.webm --contact-sheet-threshold 0.02

The threshold accepts values from 0 to 1 and defaults to 0.05. Passing --contact-sheet-threshold implies --contact-sheet. At most 100 frames are included.

Use Cases

Debugging Failed Automation

#!/bin/bash
# Record automation for debugging

# Run your automation
agent-browser open https://app.example.com
agent-browser record start ./debug-$(date +%Y%m%d-%H%M%S).webm
agent-browser snapshot -i
agent-browser click @e1 || {
    echo "Click failed - check recording"
    agent-browser record stop
    exit 1
}

agent-browser record stop

Documentation Generation

#!/bin/bash
# Record workflow for documentation

agent-browser open https://app.example.com/login
agent-browser record start ./docs/how-to-login.webm
agent-browser wait 1000  # Pause for visibility

agent-browser snapshot -i
agent-browser fill @e1 "demo@example.com"
agent-browser wait 500

agent-browser fill @e2 "password"
agent-browser wait 500

agent-browser click @e3
agent-browser wait --url "**/dashboard"
agent-browser wait 1000  # Show result

agent-browser record stop

CI/CD Test Evidence

#!/bin/bash
# Record E2E test runs for CI artifacts

TEST_NAME="${1:-e2e-test}"
RECORDING_DIR="./test-recordings"
mkdir -p "$RECORDING_DIR"

agent-browser open
agent-browser record start "$RECORDING_DIR/$TEST_NAME-$(date +%s).webm"

# Run test
if run_e2e_test; then
    echo "Test passed"
else
    echo "Test failed - recording saved"
fi

agent-browser record stop

Best Practices

1. Add Pauses for Clarity

# Slow down for human viewing
agent-browser click @e1
agent-browser wait 500  # Let viewer see result

2. Use Descriptive Filenames

# Include context in filename
agent-browser record start ./recordings/login-flow-2024-01-15.webm
agent-browser record start ./recordings/checkout-test-run-42.webm

3. Handle Recording in Error Cases

#!/bin/bash
set -e

cleanup() {
    agent-browser record stop 2>/dev/null || true
    agent-browser close 2>/dev/null || true
}
trap cleanup EXIT

agent-browser open
agent-browser record start ./automation.webm
# ... automation steps ...

4. Combine with Screenshots

# Record video AND capture key frames
agent-browser open https://example.com
agent-browser record start ./flow.webm
agent-browser screenshot ./screenshots/step1-homepage.png

agent-browser click @e1
agent-browser screenshot ./screenshots/step2-after-click.png

agent-browser record stop

Output Format

• Format follows the extension: .webm (VP8 via libvpx) or .mp4 (H.264 via libx264); other extensions get H.264 in that container
• Default frame rate: 30 fps (--fps accepts 1 to 60)
• Optional contact sheet: timestamped PNG with changed-region highlights
• Compatible with all modern browsers and video players
• Compressed but high quality

Limitations

• Recording adds slight overhead to automation, and higher frame rates add more
• Large recordings can consume significant disk space
• Distinct frames per second are bounded by how often the page repaints, so a page rendering below 60 fps records below it too
• Some headless environments may have codec limitations; an ffmpeg built without libvpx or libx264 cannot write the matching format