Back Home

最新模型

Elorian Releases Glimpse Visual Reasoning Model, Enabling Image and Video Reinspection During Reasoning

Elorian launched the Glimpse research preview on October 16, enabling the model to zoom in on images, revisit video, and use multimodal tools during reasoning. The model is available on API platforms, but official evaluations use different agents and reasoning settings; real-world latency and cost still need validation.

Alfred Percival Maudslay · Public domain · Image source
zh-Hant

Elorian released its first model, the Glimpse research preview, on October 16, focused on object tracking, spatial relationships, and understanding video events. The company says the system can revisit visual representations during reasoning and use code, image-processing, and video tools. The goal is to let the model identify uncertainty and then return to the visual evidence to check it. Official announcement

The technical focus of this workflow is to concentrate additional observation on the segments that affect the answer. In an official example involving a bird video, the model first inspected footage at eight frames per second, then increased the sampling density around a brief camera movement to determine whether the scene moved continuously or had been edited. For video annotation and event search, this offers a direction worth testing: adjust where and how densely the model observes based on the question. Demo and execution trace

In its official evaluations, Glimpse scored 83.75 on embodied spatial reasoning (ERQA), matching GPT-6 Astra in the table, but still lagged on some video-understanding tests. The models were paired with different agent execution frameworks, tools, and reasoning strengths, so these figures should be treated as comparisons of complete systems; they are not enough on their own to demonstrate an architectural advantage. Evaluation conditions

There are already concrete deployment options. Vercel AI Gateway lists the model identifier elorian/glimpse, priced at $0.60 per million input tokens and $3 per million output tokens, with a 220K context window and a 4,096-token output limit. Reasoning tokens also count toward the output limit. OpenRouter lists a 262,144-token context window. Engineering teams should confirm limits for their chosen endpoint rather than carrying settings over directly between platforms. Vercel model documentation, OpenRouter model page

The most useful next measurements are the total tokens, tool calls, and wait time required to complete a task. Repeated observation may improve recognition, but it also increases computation; Elorian has identified token efficiency as a priority for improvement. Researchers should also check tracking consistency and timestamp accuracy with Chinese instructions, and distinguish the real execution traces on the official page from human-reviewed reference answers to assess whether the model is suitable for data annotation or robot planning. Limitations and next steps

Sources

  1. Introducing Glimpse
  2. Glimpse API, Pricing & Playground
  3. Glimpse - API Pricing & Providers