Question 1

Is this just browser-use with Jev swapped in?

Accepted Answer

Closer to a port of one specific project. It is a Manifest V3 port of browser-use/jev-ultrafast with the same observation format, questions and execution rules, and the README compares it against jev-browser and browser-use side by side. Jev picks the operation and element; a small chat model writes typed values.

Question 2

Is 13 of 17 tasks good enough to trust it with real browsing?

Accepted Answer

Treat it as a demo rather than a benchmark win. Across seven rounds of the same suite the score moved 9, 10, 11, 14, 13, 13 and 13 while executor and loop bugs were being fixed, and individual tasks flip between runs. In that run two misses were OpenRouter 429s on the text model, which passed in earlier rounds.

Question 3

Will typing into fields send text the model invented?

Accepted Answer

Jev itself never writes text: it only picks the operation and the element. A small chat model turns the goal plus field context into the exact string, and the extension says outright that it never guesses field values itself. Enter is never pressed implicitly either, since a focused field gets a separate PRESS_ENTER control the model must choose.

Question 4

What does it refuse to do that the reference project handles?

Accepted Answer

Several things, listed in the README: links that open new tabs are followed, wrapped links are clicked where they render, and controls hidden under other blocks are not offered. It also dispatches input through Chrome's DevTools protocol, which needs the debugger permission that Chrome will not allow to be optional.

Question 5

How do I install and use the extension?

Accepted Answer

It is a Manifest V3 extension published on the Chrome Web Store. Install it, open the popup and type a goal; numbered badges show the elements the model can see, a status bar shows each decision and its latency, Step executes one decision at a time, and Copy trace exports the run as JSON.

Question 6

Does it need Python or Playwright?

Accepted Answer

No. It runs in the tab you already have open, in your normal Chrome profile, so there is nothing to install besides the extension: no Python, no Playwright and no second browser. That also means the cookies and logins it uses are your own.

Question 7

What Chrome permission does it need, and can I avoid it?

Accepted Answer

It dispatches real input through Chrome's DevTools protocol, which needs the `debugger` permission, and Chrome does not allow that permission to be optional. It can be switched off in Options, in which case the extension falls back to synthetic DOM events.

Jev for Chrome — chy4pro

About this project

Highlights

Quickstart

Questions about this entry

Reactions & coverage

Other listings of this project

From the Jev guides

From the Jev AI model community