Skip to main content
An autouser is a UX-research persona implemented as a Computer Use agent. It receives a stimulus (URL, screenshot, or video), navigates or inspects it the way a real first-time user would, and emits a Rating in the same shape a human rater produces.

Anatomy

System autousers are visible to every team. Team autousers are scoped to the team that created them.

Listing

The default response includes both system and your team’s autousers. Filter with ?source=system|team.

Creating a custom autouser

A new autouser starts uncalibrated — it can rate, but its scores have no inter-rater reliability data yet.

Calibration

Calibration is how an autouser learns to agree with itself across runs. We feed it a small panel of comparisons, run it N times, measure the consistency of its ratings, and either freeze the rubric (locking in stable behaviour) or iterate the system prompt. Lifecycle:
Trigger:
Watch:
Freeze when stable:
Freezing emits a calibration.frozen webhook. Downstream pipelines should listen for it before promoting an autouser to production.

Runs

When you call /v1/evaluations/{id}/run-autousers, every entry in selectedAutousers is expanded by agentCount into individual AutouserRun rows. Each row tracks:
  • status: pendingrunningcompleted or failed.
  • currentStep, currentAction, currentNarration: live worker progress.
  • inputTokens, outputTokens, estimatedCostUsd: cost telemetry.
  • artifactsPath: GCS prefix for video, screenshots, transcripts.
A failed run does not consume autouser-rating quota. A completed run produces one Rating per Comparison; total ratings = agentCount × comparisonCount.

Cost

Autouser runs price against gemini-3-flash-preview (the only Gemini SKU with native Computer Use). Typical run: 0.040.04–0.12 depending on page complexity, navigation depth, and dimension count. Use dryRun on the parent evaluation to forecast before queueing.

Built-in personas

We ship a roster of system autousers covering common roles — first-time buyer, power user, skeptical evaluator, accessibility-first user, support-call-prone novice. They are calibrated against an internal benchmark panel and updated quarterly. Custom personas always override built-ins for your team.