Annotations

Add review notes to captured sessions and tie them to timestamps, ranges, screenshot frames, geometry, sources, and downstream handoff.

Annotations are review notes attached to a captured session. They let a tester, developer, or agent preserve why a moment matters without changing the original evidence stream.

Time and range annotations

Create a point annotation for one moment or select a timeline range when the issue spans a sequence. Ranges are useful for slow interactions, FPS drops, memory ramps, repeated log clusters, and state transitions.

An annotation can retain:

  • its session ID and source;
  • a point in time or start and end timestamps;
  • label text and notes;
  • a screenshot frame ID;
  • optional normalized screen geometry;
  • related review metadata.

Screen geometry

Use screen-targeted geometry when a note concerns a visible control, map marker, clipped label, missed tap target, or other region. Geometry stays associated with the captured frame so later reviewers and agents can interpret it in the same visual context.

Time ranges and screen geometry can be combined. For example, mark the interval where FPS fell and the region of the screen that was active during the drop.

Human and agent notes

The player shows annotations created during interactive review and annotations injected through the host API. Preserve the source so a reviewer can distinguish manual observations from automated findings.

Review workflow

Use annotations to:

  • record expected and actual behavior;
  • mark reproduction steps or suspicious events;
  • focus a later agent investigation;
  • explain why a session was extracted or retained;
  • carry spatial and timeline context into an export or share.

Agents use ansight session annotations <session-id> --json to read annotation evidence and the corresponding annotation commands to create or manage notes. See CLI Commands.