Jev-Powered Browser Use Preview

Which element to act on inside a step. A reply asks exactly that: if the whole flow is already scripted, is Jev just choosing which element to click for a given step. The post does not answer, and the quote-posted demo video is where any detail would live.

No numbers at all: no latency, no cost, no task list, no success rate. The post is two lines of text wrapped around a quote-posted clip by another account, so it tells you the pairing is worth watching and nothing about how it behaves on a real site.

The preview pairs Jev with opencode's browser-use CLI, and the quoted demo comes from a separate account posting its own small demo. Neither post gives install steps or configuration, so the practical route is running the CLI yourself and pointing its decision calls at a Jev endpoint.

The framing treats browser use as a series of classification tasks: given a goal, which buttons would advance it. The post does not say what handles typing, long-form instructions, or recovery when a click misses, so it is not a picture of a fully unattended agent.

dax, who builds opencode at anomalyco and describes himself as not the CEO, posted it on 16 September 2026. The post lists 371.3K views, which is the reach a two-line speed impression got.

It quote-posts Filip, who says testing apps with Jev and opencode will be very fast and attaches a small demo. Neither the poster nor the quoted author publishes install steps, latency, cost or a task list.

One reply describes browser use as really a series of classification tasks: given a goal, which buttons are most likely to solve it in the UI. That is the clearest explanation in the thread of what Jev is doing, offered as a reframing rather than a measurement.