COMMUNITY OBSERVEDMetric claims: AUTHOR REPORTEDSOURCE AUDITED🤖 Jev Agent⚡ Jev Skills

Jev Browser

A Jev-driven browser agent exposed as an MCP server, CLI, or library.

Overview & result

The project gives Jev a bounded set of page actions and lets it pick one step at a time while code controls budgets, recovery, and stop conditions.

From the original post

Fast and very cheap browser use using TypeSafe's Jev model.

Give jev-browser a task and a URL.

It drives a real headless browser through an MCP server, CLI, or library. TypeSafe's Jev model picks one action per step from the page's clickable, typeable, and selectable elements, and scores how likely it is that the goal is met or the run is stuck. Code owns the loop: budgets, recovery, stop gates. You get the final page, a step trace with confidences, console errors, and a screenshot.

— Joey Kudish

How Jev fits in the loop

  1. Turn clickable, typeable, and selectable elements into candidate actions.
  2. Ask Jev to choose the next action.
  3. Score whether the goal is complete or the run is stuck.
  4. Keep control flow and safety budgets in ordinary code.

How to reproduce

  1. Clone the repository and follow the author's current setup instructions.
  2. Provide a TypeSafe API key locally; never expose it in client-side code or commit it to GitHub.
  3. Run a bounded browser task, record the page states and choices, then compare cost, latency, completion, and failure behavior.

Why this build matters

It demonstrates the exact thesis behind JevForAgents: Jev can be the decision layer inside an agent loop while deterministic code owns execution.

Reported performance

Reported by author

Cost: $0.0016 for one reported Wikipedia navigation example

Latency: ~4s end-to-end for that reported example

Reported by the project author for a specific real-site example; not independently tested by JevForAgents.

Limitations

  • The demo and performance figures come from the project author.
  • Browser pages change, so element selection and task completion can regress.
  • Sensitive answers and irreversible actions should remain behind explicit user confirmation.

Patterns