Skip to content

Jev Browser Bridge

Agent bridge that connects any CDP-speaking browser to Jev by reading the DOM instead of the rendered layout, so headless or non-drawing browsers can still drive CLICK, TYPE_TEXT, SELECT, WAIT, DONE, and BLOCKED steps.

Stars
10
Language
Python
License
APACHE-2.0
Published by
Community
Author
lexmount
Last verified
Oct 2026

lexmount/jev-browser-bridge

Organization repository on GitHub

View on GitHub

Plug any CDP browser into Jev — cloud, local or self-hosted, including browsers that never draw a page.

Forks
0
Last pushed
Updated Oct 2026

Repo stats from the GitHub API, cached Oct 2026.

About this project

Cloud, local or self-hosted. Chromium or not. Even browsers that never draw a page. If it speaks CDP, it runs Jev. One task, one Jev model, four browsers, each read two ways — recorded runs on a shared clock. Pictures are each browser's own screenshot; Lightpanda answers with a placeholder and Obscura has no screenshot at all. The position-based reader finishes on the browsers that draw pages; Jev Browser Bridge finishes on all four . Open the player to pause, scrub and read each run's raw trace.

Quoted from the project's README. Read the full README.

Highlights

  • Each step builds an element table and asks Jev for operation plus target in one request.
  • Clicks dispatch on the element itself, so there is no coordinate to go stale.
  • Long pages are split into rows and retrieved against the goal up to a character budget.
  • Same-named controls are labelled by location; script-bound spans surface via pointer styling.

Watch out

A small text model is only needed for goals that type into a field, and MiniWoB++ tasks needing pointer position, drag, drawing, colour, or password are excluded. Copy reviewed against the repository README on 2026-10-04, not from running it.

Questions about this entry

Short answers drawn from the linked project or page.

More Jev resources like this

62GitHub stars
Simulation study that drives one xArm7 apple-to-plate task with Jev, a large reasoning model, and a small model through identical incremental controls.
Jev Demos & Experiments#community#jevbest#catalog-import
114GitHub stars
Browser agent where Jev picks each action from indexed page candidates while an LLM plans and reads, returning cited answers or schema-checked data with credential controls.
Jev Demos & Experiments#community#jevbest#catalog-import
4GitHub stars
Browser-use layer for CLI coding agents: Jev picks the operation and target element in one round trip per step, exposed over MCP with a CLI, a Python API and an HTTP server.
Jev Demos & Experiments#community#jevbest#catalog-import
2GitHub stars
A Python decision layer for browser and desktop automation: your code observes the surface, builds the candidate list and verifies the result, and the model only picks one id per step.
Jev Demos & Experiments#community#jevbest#catalog-import
0GitHub stars
A local Python browser automation UI that turns a URL and a plain-language goal into bounded actions, with Jev picking the next operation from observed candidates and a separate text model used only to fill fields.
Jev Demos & Experiments#community#jevbest#catalog-import
1GitHub stars
A Streamlit Tetris where the engine enumerates every legal placement, Jev picks one typed placement ID, and Python verifies rotation, column and exact occupied cells before the piece is allowed to lock.
Jev Demos & Experiments#community#jevbest#catalog-import

From the Jev guides

Original write-ups on what this entry is for.

A game tick is a state plus a legal action list. How Clash Royale, Minecraft, and the earlier Mario, Pokémon, StarCraft, and drone loops ask Jev one step at a time.
Jev Demos & Experiments#gaming#agents#control
Read article
Back to all resources

From the Jev community

Posts from builders shipping with Jev right now.

Follow @typesafeai