Session Capture

Capture live sessions through the resident host and preserve logs, screenshots, telemetry, touches, visual trees, annotations, state, and artifacts.

A session is the host’s time-aligned record of a paired app connection. The local player lists connected and historical sessions and refreshes the selected live session as new evidence arrives.

Start capture

  1. Start the resident host with ansight host run --open.
  2. Launch an enrolled development or QA build.
  3. Confirm the app appears as a Live session in the player.
  4. Reproduce the behavior while the host remains running.

Capture begins when the paired app opens its eligible connection. After the app disconnects, the same session remains available as a recorded capture.

Captured evidence

A session can contain:

  • app, platform, device, runtime, and capture metadata;
  • logs, exceptions, lifecycle events, and network request metadata;
  • telemetry channels and samples;
  • screenshots and replay frames;
  • visual tree snapshots;
  • touch input and inferred gestures;
  • annotations and review metadata;
  • artifact snapshots and captured files;
  • linked test traces and analysis results.

The exact evidence depends on the SDK packages, runtime configuration, and tool guard enabled by the app.

Local intake

Normal app-to-host intake stays on the trusted development network and is stored on the developer machine. It does not require a cloud relay. Sharing, cloud storage, and hosted computation are explicit follow-up operations.

Focus a capture

Use the timeline to mark an interval, create an annotation, or extract a smaller session. Extraction preserves the source capture and is safer for a focused handoff than destructive trimming.

Start with ansight session list --connected --json and ansight session show <session-id> --json, then use session logs, network, metrics, images, touches, trees, artifacts, and annotations for deeper review. See CLI Commands.