Guide agents, developers, and testers to the right evidence

Point agents toward problems to investigate and direct developers and testers to the exact timeline moments and screen areas that need attention.

Use annotations to tell an agent which problem to investigate and show developers and testers where to look. Attach a note to a timeline moment, a range, or an area of a captured screenshot so the observation stays with its evidence. Notes preserve what you saw and why it matters without changing the original capture.

Time and range annotations

To guide someone to an interaction that needs investigation:

  1. Open the captured session in the player and find the relevant interval.
  2. Choose Session tools, then drag across the timeline to select the range. You can also hold Shift while dragging.
  3. Choose Add annotation. In Comment, describe the problem, the expected behavior, and what the reviewer should investigate.
  4. Choose Save annotation, then give the session ID to your agent or teammate and direct them to the note.

For example:

Checkout stays on the address screen after I tap Continue. Expected: the payment screen opens. Review the taps and navigation logs in this interval to find where the transition stopped.

Use a point annotation for one moment or a range for a sequence, such as a slow interaction, FPS drop, growing memory use, or repeated errors.

Mark an area of a screenshot

When a note concerns a clipped label, missed tap target, map marker, or other visible area, show the captured screenshot and hold Shift while dragging over that area. Add your comment and choose Save annotation. The mark stays attached to that screenshot so agents, developers, and testers can identify the same part of the screen later.

Annotations can include both a time range and a screen area. For example, a note can identify the interval where FPS fell and the area being used during the drop.

Human and agent notes

People can add notes in the player, and agents can add them through the host API or CLI. Keep the note’s source so later reviewers can distinguish a person’s observation from an automated finding.

Review workflow

Use notes to direct the next investigation or review:

  • Give an agent the session ID and ask it to read the annotations before investigating the marked problem.
  • Direct developers and testers to the specific interaction or screenshot area, including what happened and what should have happened.
  • Mark reproduction steps, suspicious events, or areas of interest to revisit.
  • Explain why a session was extracted or retained, and keep those notes with the evidence when you export or share it.

What a note keeps

An annotation can retain the session and authoring source, its time or range, comment text, a reference to a captured screenshot, and a marked screen area. Screenshot positions are stored relative to the image size so the mark stays aligned when the player displays the image at a different size.

Agents can start with ansight session annotations <session-id> --json to read the notes for a session, then inspect the referenced times and screenshots. See CLI Commands for commands to create or manage notes.