With JEV at this speed, once it's hooked up to Browser Use

@Manorgw Man ting · Sep 19, 2026 · case #498370 · listed via Jev Hub

Still from the clip posted with this case; watch it in the original post on X.

Connected Jev to Browser Use so DOM clicks become discrete multiple-choice decisions instead of slow LLM prose.

The original post, translated

With JEV at this speed, once it's hooked up to Browser Use, isn't it just absurd?? Earlier, watching GPT and Claude control the browser, the experience was really mediocre, so slow it drove people crazy, and it would freeze up all the time in the middle... In the end, having a large model go on and on to operate a webpage is just using a sledgehammer to crack a nut. Clicking a button on a webpage is essentially a discrete multiple-choice question, and it doesn't need AI to know how to write poetry at all. JEV gets the DOM

Show the original post in its source language ▾

JEV 这速度，一接上 Browser Use 是不是直接离谱了？？早先看 GPT、Claude 操控浏览器，体验真心一般，慢得让人抓狂，中间还动不动卡死…… 说到底，让大模型长篇大论地去操作网页，本来就是杀鸡用牛刀。网页上点个按钮，本质就是道离散多选题，压根不需要 AI 会写诗。 JEV 拿到 DOM

The post above is a machine translation from zh; the untranslated text is in the fold-out.

Engagement when collected

Likes0

Bookmarks0

Reposts0

Replies0

Quotes0

Numbers are a snapshot taken from X when the case was added to the library (schema v1, collected 2026-09-19); they will not match today.

Where this case fits

Filed under browser & computer use. In the pattern Jev is built for, the model answers a bounded question per step — and ordinary code acts on the answer, because the answer is already a value rather than a paragraph. Other posts in the same family are on the browser & computer use page.

🌐 Browser & computer use