Jev browser control selection matches a user's navigation goal to a control in a supplied snapshot. Our original fixture contains three links: plan information, API documentation and contact support. The model selects a label. The offline consumer returns the corresponding element ID and href from the local fixture, so the destination is inspectable without clicking it.
A phrase such as read the API setup may differ from the visible label API documentation. That semantic match is the task here. The href and elementId have a different role: they preserve which control the application actually observed. A fluent destination description cannot create a fourth element or authorize a purchase that the snapshot never offered.
An API-collected X post about Jev selecting browser actions inspired the example. We read related maintainer repositories to understand where their extraction and execution loops sit. This page tests a single text decision over a synthetic snapshot. It does not run Browser Use, connect to your tabs, observe screenshots or reproduce the post's timing and cost comparisons.