CodeariaAcademy
GitHub repositorycommit this monthAutomationDevelopment

Jev Ultrafast

22k

A browser agent from the browser-use team where each step is decided not by an LLM but by the Jev model: which action, on which element. A Google Flights search in 7.1 seconds, MIT.

We have not run it ourselves: described from the docs and the repository.

In numbers

a Google Flights search
time, over three pairs of runs
licence

What it is

A typical browser agent sends a screenshot or a page tree to an LLM at every step and waits for it to write out where to click. Jev Ultrafast, a new repository from the browser-use team, works differently. The page becomes a numbered table of elements, and the TypeSafe Jev model picks what to do and on which element in a single request. A generative model only steps in when something has to be typed.

The difference from browser-use, its neighbour in this catalogue, is the approach. There the agent is general-purpose and thinks with a large model at every step; here it is a narrow, fast loop where the LLM barely takes part. It is the same move we covered in our article on Jev: binary and selection decisions are taken off the generative model, and the agent gets faster for it.

How it works

page → table
The page becomes a numbered list of elements; there are no screenshots in the main loop.
TypeSafe Jev
Picks the operation (CLICK, TYPE_TEXT, SELECT, scrolling, WAIT, DONE) and the element number in a single request.
OpenRouter
Only needed when something has to be typed, such as a city name; the example uses inception/mercury-2.5 via OpenRouter.
DOM check
The model's output never becomes a selector, coordinates or code: every action is bound to a real DOM node and re-checked before the click.
uv sync
Chrome attaches through Browser Harness and you need a TypeSafe key plus one for the text model; it ships with a local inspector showing operation probabilities and an Agent library for your own tasks.

Know before installing

The demo searches for flights but does not pick or book a ticket. The 7.1-second clock starts after the first page load, and the authors themselves describe the "−25% time" figure as three pairs of runs on one task, not a reliability benchmark.
Frames, shadow DOM, canvas, file uploads and pop-up tabs are outside the MVP for now.
The full cost of a task, including the Jev requests, is not disclosed.

Comments