Community · E2 · artifact verified

Search Google Flights in seconds

A browser agent turns the visible DOM into an indexed action space and uses Jev to choose the next operation and compatible target.

01 · Role in the system

What Jev does here

Jev receives a compact table of visible controls and answers an operation Choice plus speculative target Choices in one request. Code reads only the target that matches the selected operation, resolves it back to an observed DOM node, checks freshness and occlusion, and executes it. A separate small text model is called only when the chosen operation needs free text.

02 · Control boundary

Where Jev sits

Browser state to parallel operation and target choices; deterministic code validates and executes one branch.

Code owns the loop, permissions, thresholds, validation, and side effects. Jev owns only the bounded judgments described above.

03 · Known limits

What this evidence does not prove

  • The published timing covers one browser profile and one task, not a general reliability benchmark.
  • Frames, canvas, uploads, pop-up tabs, and arbitrary keyboard widgets remain outside the MVP.

04 · Attribution

Public sources

This is a Community record: the project was published by a third-party community author.