First run onboarding
Install the runner, connect the workspace, launch a scoped test.
The first-run path stays explicit: install the runner, see the current prerequisite, and understand what artifacts come back from the first successful workflow.
1
Install local runner
Use the desktop runner on the same machine that will capture browser, HTTP, and CLI evidence.
2
Open the workspace
Create the first project, connect sign-in, and define scope before any workflow begins.
3
Launch a starter run
Run a guided auth or smoke workflow first so newcomers see a successful path immediately.
After sign-in
Create your first project workspace
Define scope and guardrails
Trigger a guided starter run
Next action
Choose your runner
Pick the correct installer first, then continue to workspace sign-in and create your first project.
Device status
We could not detect your OS
Windows and Linux are available now
Runner requirement
Keep the local runner installed on the same machine that captures evidence.
First safe objective
Start with homepage auth or smoke checks before moving to deeper workflows.
Expected output
A replayable transcript, screenshots, traces, and a report-ready export.
Why this flow works
- One decision per screen.
- No redirect surprise before the runner path is explained.
- Every screen tells the newcomer what happens next.
Quick links
Keep the flow short and explicit.
Once the runner is installed, the workspace exposes one guided starter workflow by default. That is the fastest path from curiosity to confidence.