Keep sessions, tests, and performance history together
Move between captured evidence, test results, and app performance history in the local player, with playback and linked traces tied to the session you select.
Use the local player to review an app’s captured evidence, run its tests, and check performance history in one browser UI. Within a selected session, move between playback, simulator control, and linked test traces while keeping the app and capture in context.
Global areas
| Area | What it provides |
|---|---|
| Sessions | Live and recorded session selection, timeline playback, screenshots, logs, telemetry, annotations, trees, artifacts, network evidence, and linked traces. |
| Tests | Source-controlled test discovery and execution plus persisted run history and model/tool audit traces. |
| Apps | Registered apps, current live-session state, and app-scoped context. |
| Trends | Monitored metrics grouped by app, including current values, references, deltas, decisions, history, and rebuild actions. |
| Manage → Devices | Supported local simulator and emulator discovery, preparation, and control. |
| Manage → Session storage | Session import, export, retention, and cleanup. |
| Manage → Host health | Diagnostics, permissions, logs, and host readiness. |
| Manage → Settings | Local host configuration exposed by the installed CLI version. |
Available areas are capability-driven. The player hides controls when the running host does not expose the corresponding service.
Session context
Selecting a session keeps the relevant app and capture in context while you move between playback, simulator control, App Graph progress, and linked test traces. Connected simulator or emulator sessions can switch between Simulator and Playback without stopping capture.
Agent boundary
The player does not embed or manage coding-agent conversations. Give Codex,
Claude, Cursor, CI, or another terminal-capable agent access to the ansight
CLI instead. Use source-controlled workspace definitions for
tests, tasks, triggers, Trends definitions, schemas, and sanitizers.
This separation keeps the browser UI focused on host state and evidence while agents consume the same services through stable JSON contracts.