Visual Review

Every finished ticket, shown.

An agent records the change in your product and puts a captioned video on the Jira ticket. A person approves.

Talk to a human Watch a real one
  1. Recorded
  2. Captioned
  3. Measured
  4. On the ticket
  5. Approved

A real one

The film of a real ticket, as it went on Jira.

OFIR-1630Done

A bell in the header shows what needs you

evidence.json

  • AC-1 0:03
  • AC-2 0:15
  • AC-3 0:26
  • AC-4 0:26

4 of 4 criteria shown

On Loomcaptioned · 0:41 · 3 chapters

Real film, as it went on the ticket. Ticket OFIR-1630 on XALT’s Event Chief of Staff, recorded on a staging test system on 20 Oct 2026. 41 seconds, no sound.

The new bottleneck

Agents write code in minutes. Checking it should not take longer.

On the ticket

Everything the reviewer needs, on the ticket.

OFIR / OFIR-1630 video-demoDone

A bell in the header shows what needs you

Attachments

OFIR-1630-film.mp4captioned · 0:41
OFIR-1630-evidence.mp4untouched · 0:09
{ }
OFIR-1630-evidence.json4 criteria

Activity

Visual Reviewadded a comment

Film, with the reason at each beat: Loom

  • 0:03A bell in the header counts what waits
  • 0:15Tapping the bell opens what needs you
  • 0:26Agent status opens from the bell

Per criterion (seconds in the film)

AC-1shown0:03bell in header = false → true✓

AC-2shown0:15panel shown = true · page unchanged = "#chat"✓

AC-3shown0:26status row = true · status view = "status"✓

AC-4shown0:26elements wider than viewport = 0 → 0✓

What the film does not show:

  • How the bell counts each entry: unit tests
  • Keyboard and 44 px tap targets: e2e tests

Real ticket on XALT’s Event Chief of Staff · staging test system · 20 Oct 2026 · layout redrawn

Rules

Four rules every video follows.

  1. Measured, not claimed

    The ticket shows what was measured, like bell in header = false → true.

  2. Edits are visible

    Sped-up parts are labelled, like “Getting there 3×”; pauses say Paused. The raw take stays raw.

  3. A person signs in

    The agent hands the browser over and waits. It never types a password.

  4. A person approves

    The agent drafts the video. A person decides, and the ticket status is never changed for you.

Where teams use the videos

One video, many readers.

One video per ticket
AcceptanceSprint reviewRelease notesBug reportsOnboardingSales and support

Start here

Try it on three of your tickets.

In your Jira and your Loom. Three finished tickets get their video, and your team decides whether reviews got faster.

Talk to a human

30 minutes with Philipp Göllner, CEO. No slides.

Not sure where agents fit in your teams? The AI maturity audit has seven questions, and you get your wave, your weakest capability and the next step.

Start the AI maturity audit