// Pre-release onboarding test via Chrome browser automation. Tests the full new-user flow — provider selection, workflow picker, and streaming all three starter workflows. Use when asked to test onboarding, first-run experience, or starter workflows.
| name | onboarding-test |
| description | Pre-release onboarding test via Chrome browser automation. Tests the full new-user flow — provider selection, workflow picker, and streaming all three starter workflows. Use when asked to test onboarding, first-run experience, or starter workflows. |
cd frontend && npm run buildUse port 8080 (not 8000 — the OSC server binds to the same port as the HTTP server and port 8000 is commonly in use).
mkdir -p /tmp/scope-onboarding-test/data /tmp/scope-onboarding-test/models
lsof -ti:8080 | xargs kill -9 2>/dev/null
DAYDREAM_SCOPE_DIR=/tmp/scope-onboarding-test/data \
DAYDREAM_SCOPE_MODELS_DIR=/tmp/scope-onboarding-test/models \
SCOPE_CLOUD_APP_ID="daydream/scope-livepeer/ws" \
uv run daydream-scope --port 8080 > /tmp/scope-onboarding.log 2>&1 &
for i in $(seq 1 30); do curl -s http://localhost:8080/health > /dev/null 2>&1 && break; sleep 1; done
Navigate to http://localhost:8080. The onboarding screens appear in this order:
Provider selection — "Welcome to Daydream Scope" with "Use Daydream Cloud" and "Run Locally" cards. Select Cloud, click Continue.
Usage Analytics dialog — appears as a modal overlay. Click No thanks (privacy-preserving default).
Onboarding style — "Teaching Mode" vs "Simple". Pick either, click Continue.
Workflow picker — "Pick a workflow to get started" showing 3 starter workflows:
Select one, click Get Started.
Graph editor with onboarding tooltips — Two tooltip popups appear sequentially over the Sink/Run area:
IMPORTANT: These tooltips intercept clicks on the Run button. You MUST dismiss both tooltips (using read_page to find the Next/Done button refs) BEFORE clicking Run.
Click Run — use read_page(filter="interactive") to find the Run button ref and click it. Do NOT click by coordinates near the tooltip area.
Click Workflows in the top nav bar to reopen the workflow panel. The "Getting Started" section shows all three starter workflows. Click a different one to load it, then click Run.
| Workflow | Nodes | Notes |
|---|---|---|
| Mythical Creature | Source, VACE, LoRA, longlive, rife, Sink | Style LoRA, video input |
| Dissolving Sunflower | Source, video-depth-anything, VACE, LoRA, longlive, rife, Sink | Depth map, video input |
| LTX 2.3 | Primitive (String), ltx2, Sink | Text-to-video, no Source node |
lsof -ti:8080 | xargs kill -9 2>/dev/null
rm -rf /tmp/scope-onboarding-test
Test Scope locally in Livepeer mode end to end using a prebuilt `go-livepeer` artifact from the `ja/serverless` PR, `uv run --extra livepeer livepeer-runner`, and Scope. Use when the user mentions Livepeer mode, `livepeer-runner`, or local serverless testing. Pair with `testing-scope-mcp` when the test path should be driven through Scope's MCP server.
Verify fal app behavior end to end: deploy aliases, test public websocket endpoints, and inspect live runners. Use when working with `fal deploy`, `fal run`, `fal runners exec`, or websocket readiness.
Test Daydream Scope through its stdio MCP server, including disconnected startup, `connect_to_scope`, direct Python stdio client fallback, and lightweight smoke tests. Use when testing Scope via MCP, debugging MCP registration, or when a workflow depends on `connect_to_scope`, `load_pipeline`, `start_stream`, or `capture_frame`.