How many times the run bounced to an identity provider and was recovered
by the auth-detour watchdog. 0 on runs that never detoured. A
per-run infrastructure-health signal: a non-zero count on an otherwise
successful run still flags a flaky session, and it's the count that
decides the AuthDetour termination.
OptionalErrorError details (populated when Status is 'Error')
OptionalFailureCompact structured memo of why a non-passing run failed, set only
on non-Completed terminals. The driver's retry policy feeds it back as
RunComputerUseParams.PreviousAttemptSummary so a retry is
non-blind ("previous attempt failed because X; avoid Y"). Undefined on a
clean pass.
OptionalFailureMachine-readable reason for a non-success terminal state, when the engine
can name one. Distinct from the coarse Status: e.g. a
Failed run may carry 'LoopDetected'. Consumed by the failure
classifier and the retry policy (which can decline to retry known
classes). Extended as more classes are detected.
OptionalFinalThe last judge verdict (if the judge was consulted)
Final screenshot captured (base64 PNG)
Final URL the browser was on when the run ended
OptionalReplayReplay telemetry, set only when the run executed on the replay tier via ComputerUseEngine.Replay. Undefined for LLM-tier runs. Carries per-step hit/healed/diverged outcomes for the UI-drift report.
Terminal status of the run
Complete history of all steps executed
Whether the run achieved its goal
Total wall-clock duration of the run in milliseconds
Total number of steps executed
OptionalTraceFilesystem path to the forensic trace written for this run, set only when tracing was requested (via RunComputerUseParams.TracePath) AND a trace file was actually written. Undefined otherwise. The caller decides whether to keep it (e.g. retain-on-failure) or delete it.
Complete result of a Computer Use engine run.
Contains the full step history including screenshots (as base64 strings), all actions executed, tool calls, judge verdicts, and timing information.
Layer 1 holds everything in memory. Layer 2 (MJComputerUseEngine) persists screenshots via AIPromptRunMedia entities and logs via MJ's audit system.