Lode

Stand on the shoulders of giants.

Open the curator →
Source
arXiv
Published
Runtime
0:00
Snippets
4

A conversation between

OmniAssistBench: Assistant-style Interaction Benchmark for Omni-LLMs

Waveform of the source interview with highlighted segments per snippet.
0:00 0:00

§02

Snippets

  1. Interactive assistants must actively combine visual states, user goals, and prior knowledge; static offline datasets cannot accommodate dynamically changing interaction paths.

    Current benchmarks miss the core challenge: guiding users through a *specific* sequence of steps when many valid paths exist.

  2. The dataset is constructed by reverse-engineering Internet videos: deducing logical user goals and segmenting videos into multi-turn clips to simulate continuous interactions.

    This approach scales evaluation to ~1000 person-hours, but introduces synthetic artifacts—real user behavior may differ.

  3. Models struggle with visual prompts (hand gestures), fail to maintain historical context during multi-turn interactions, and cannot delay response until the target event occurs.

    These failures directly undermine reliability as real assistants—users expect perception of nuanced cues and temporal awareness.

  4. Gemini-3-Pro achieves 66.4/100 while Qwen3-Omni-Instruct reaches 51.2/100, indicating substantial gaps in assistant capability.

    Even frontier models are not yet reliable video assistants, establishing a clear research target for the community.

§03

Synthesis

The Problem: You Can't Benchmark a Real-Time Assistant with a Static Dataset

Video understanding models have improved dramatically, but there's a blind spot: evaluating them as interactive assistants. Traditional benchmarks measure passive comprehension—"describe this video." But a real assistant must do something harder: watch continuously, understand what the user wants, predict what they'll do next, and guide them step-by-step toward a goal. Every response the model gives changes what the user does afterward, creating branching paths that no fixed dataset can capture. Existing Omni-LLMs (models that handle text, images, video, and audio together) have no rigorous way to measure interactive performance.

The authors' solution is OmniAssistBench, a dataset and evaluation framework built specifically for multi-turn, goal-driven video interactions. The key insight: rather than trying to capture every possible path through an interaction, they lock models into following one correct path by providing predefined "priors"—visual landmarks or state information extracted from the source video. This makes evaluation deterministic and reproducible, while still forcing the model to provide moment-by-moment guidance that adapts to user actions.

How They Built It (and Why It's Hard)

Genuinely interactive video data doesn't exist at scale—nobody has thousands of recorded sessions where users follow instructions while being corrected in real time. So the authors reverse-engineered existing Internet videos. They watched clips, inferred plausible user goals ("learn to fold origami," "repair a bicycle"), then worked backward to identify what an assistant should say at each step. They segmented videos into multi-turn exchanges, creating scenarios where a user takes an action, the model responds with guidance, and that response should steer the user toward the next correct frame.

This labor-intensive process consumed over 1,000 expert person-hours. The rigor matters: it ensures that "correct" responses are unambiguous (tied to specific video frames and predefined goals), not subjective.

What the Results Reveal

The leaderboard is sobering. Gemini-3-Pro (proprietary) scores 66.4 out of 100; Qwen3-Omni-Instruct (open-source) reaches 51.2. These are not failing grades, but the gap to reliability is wide. The breakdown of failures is telling:

  • Visual prompts fail: Models miss hand gestures and other visual cues meant to signal intent.
  • Context degradation: Over multiple turns, models forget earlier parts of the conversation or lose track of the user's progress.
  • Timing errors: Models respond too early or too late, unable to wait for a target event (e.g., "tell me when the user's hand reaches the bucket").

In other words, current Omni-LLMs can parse individual frames and understand language, but they struggle with the sequential, context-aware reasoning that real assistance demands.

Why This Matters

As voice assistants and AR glasses proliferate, there's genuine demand for models that can watch a live scene and guide users in real time. This benchmark fills a concrete gap: it's the first rigorous evaluation framework for this use case. The authors have shown not just where models fail, but how they fail—providing a roadmap for improvement. Without OmniAssistBench, progress on interactive video understanding would be invisible.

Mine your own.

Lode is a workbench, not a feed. Paste a YouTube URL. The model proposes a transcript, a set of quote-grounded snippets, a synthesis essay, and the fan-out. You decide what stays.

Open the curator