Anatomy
System autousers are visible to every team. Team autousers are scoped
to the team that created them.
Listing
?source=system|team.
Creating a custom autouser
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:
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:pending→running→completedorfailed.currentStep,currentAction,currentNarration: live worker progress.inputTokens,outputTokens,estimatedCostUsd: cost telemetry.artifactsPath: GCS prefix for video, screenshots, transcripts.
agentCount × comparisonCount.
Cost
Autouser runs price againstgemini-3-flash-preview (the only Gemini
SKU with native Computer Use). Typical run: 0.12 depending on
page complexity, navigation depth, and dimension count. Use dryRun
on the parent evaluation to forecast before queueing.