QA that runs when nobody’s watching
Harness browsers verify the page you just built — while you sit there. VidMee’s monitors, sweeps and CI gate keep checking after the session ends: on a schedule, on every deploy, against baselines, behind logins — from any harness, with no seat open anywhere.
Why unattended QA
In-session verification is table stakes now, and the always-on agent products that go further keep the capability inside their own walls and plans. VidMee’s position: unattended checking is a layer, not a product you switch to. Any agent (or plain curl) can schedule a standing check; the check keeps the same visual memory, login vault and verdict engine as every other VidMee call.
Monitors: a standing check in one call
A monitor turns any one-shot operation into a scheduled standing check with run history and change detection. Create it with the key you already have (a key can only schedule what it’s scoped to run):
curl -X POST https://api.vidmee.ai/v1/monitors \
-H "Authorization: Bearer $VIDMEE_API_KEY" -H "content-type: application/json" \
-d '{
"name": "pricing-page-nightly",
"operation": "inspect",
"input": {"source": "https://your-site.com/pricing/"},
"interval_seconds": 86400,
"baseline_name": "pricing-approved",
"webhook_url": "https://your-app.com/hooks/vidmee",
"notify_on": "change"
}'
GET /v1/monitors lists them, GET /v1/monitors/{id}/runs is the full run history (what each run found, what changed, what was notified), PATCH pauses, DELETE removes. Every run is a normal verdict: UI/UX findings, real axe-core WCAG, runtime errors, and a diff against the named baseline.
The CI gate: verdicts on every deploy
A drop-in GitHub Action runs inspect against your preview URL on every pull request and posts the verdict + findings as a PR comment — gate merges on it if you like. Copy the workflow from the API docs (also shipped in the repo as vidmee-visual-qa.yml): add a VIDMEE_API_KEY secret and a PREVIEW_URL variable, done.
Nightly sweeps: whole-site QA in one call
sweep_site crawls the site and judges every page — per-page findings plus a severity rollup. Baselines live in visual memory, so tonight’s sweep diffs against last-known-good instead of re-judging from scratch. Put a sweep behind a monitor and the whole site re-checks itself on schedule.
Signed webhooks
Completions and monitor notifications arrive as webhooks signed with HMAC, so your receiving agent can verify the result really came from VidMee before acting on it. Long-running jobs also block internally — agents never poll.
Standing sessions
Open a session with standing: true (POST /v1/browser/sessions) and it
stays available for hours instead of minutes (default 8h idle / 12h max, tightly capped per project)
— so repeated checks against the same authenticated app skip the open-and-restore cycle. Every use
is recorded: GET /v1/browser/sessions/{sid}/audit returns the session’s touch log
(timestamp + operation), so a standing session is a purpose-bound, auditable identity, never an
invisible always-on browser. Standing sessions still expire; VidMee is not a persistent computer.
Behind logins, unattended
Vaulted sessions work in monitors too: log in once, save_login("prod-dashboard"), and the nightly check opens already authenticated — encrypted at rest, resumed by name, never your personal browser. This is the combination harness browsers structurally don’t offer: authenticated + remembered + unattended, from any harness.