Skip to main content
After every test run, FinalRun saves a full set of artifacts to disk so you can diagnose failures, replay executions, and track results over time. You can browse these artifacts directly on the filesystem or through the local report UI, which adds video playback, log search, and step-by-step screenshot browsing.

​
Artifact layout

Each run writes its artifacts to:
The <workspace-hash> is derived from your project directory, so each repository gets its own isolated artifacts folder.

​
Listing recent runs

Use finalrun runs to list local reports for the current workspace:

​
Opening the report UI

The local report UI lets you browse run artifacts with video playback, device log search, and step-by-step screenshots.
FinalRun starts a local web server (or reuses an existing one) and opens the report UI in your browser. The UI shows all runs for the current workspace.
Run finalrun start-server immediately after a test failure to replay the recording, step through screenshots, and search device logs — all in sync. This is the fastest way to understand what the AI agent saw on screen at each step.

​
Report UI features

Video playback

Watch the full screen recording of any run. Scrub to any moment to see exactly what was on the device.

Step-by-step screenshots

Browse per-action screenshots alongside the agent’s action details for each step.

Device log search

Search and filter device logs (logcat or log stream) captured during the run. Filter by log level to focus on errors and warnings.

​
Managing the server

​
Targeting a different workspace

All report commands accept --workspace <path> when you want to inspect runs from a project other than the current directory:

​
Reading result.json

result.json is the canonical record of a run. It contains the overall test outcome (pass or fail), a human-readable failure message, and step-level results that map directly to the entries in actions/ and screenshots/. When your AI coding agent reads artifacts after a failure, result.json is the first file it reads to identify which step failed and why.
When the /finalrun-use-cli or /finalrun-test-and-fix skill diagnoses a failure, it reads result.json, the matching actions/ entry, and the screenshot at the failed step before suggesting any fix. You can do the same inspection manually using finalrun start-server.