Skip to content
Metatext Decide — typed decisions for your agents, with a probability on every answerGet early access
Metatext
Sign Up

browser-use-with-jev

Lets Jev choose concrete browser actions while Codex or Browser Use's engine handles generation, recovery and final verification.

ProjectprototypeMIT
View on GitHub ↗

Overview

Browser Use with Jev lets TypeSafe Jev choose from concrete browser actions while a host handles generation, recovery and verification. In Codex desktop it defaults to the visible in-app browser via Codex Computer Use and a bundled JavaScript helper adapted from the community jev-browser-use project. A standalone mode keeps the upstream Python Browser Use engine, unpatched, in a separate browser, with the current conversation or a configured API model as host.

It was motivated by Browser Use's own jev-ultrafast experiment and its dynamic, indexed action space. The README labels it early alpha: offline integration tests pass and the bridge has been tried on a local form, but broad site coverage and comparative benchmarks are pending, and moving most routine decisions to Jev is a goal rather than a measured claim. It is independent of Browser Use and TypeSafe.

What the decision model decides

TypeQuestionAnswers
ChoiceWhich concrete browser action should be taken next?indexed actions on the page

How it works

  1. Host observes the page
  2. Indexed action candidates go to Jev
  3. Jev picks one; the host executes
  4. Host handles text generation, recovery and final verification

Strengths

  • Keeps Browser Use's engine unchanged
  • Works in the Codex sidebar
  • Clear separation of decision and execution

Caveats

  • Early alpha
  • No comparative benchmarks yet

Getting started

Install the browser-use-with-jev skill for Codex and set your TypeSafe key.

At a glance

Type
Project
Status
prototype
Language
Python
Runtime
Codex skill / Browser Use
Has code
yes
Has tests
yes
License
MIT

Use cases and integrations

How curated lists describe it

Frequently asked questions

Does it patch Browser Use?

No, it keeps the installed engine unchanged.

Is the speedup measured?

No, the README says it is a goal, not a measured claim yet.

Where does it run?

In Codex's sidebar browser or as standalone Browser Use.

Related projects

  • jev-browse (0x7067)

    Agent-plugin browser tool where Jev picks one operation and one row from a numbered page table; a small LLM only writes typed text.

    ProjectbetaTypeScript
  • jev-browser-control

    Chrome extension plus MCP server so Claude or Codex can drive your real Chrome, with Jev picking each click in about half a second.

    MCP serverbetaTypeScript
  • jev-browser-skill

    Chinese-language Codex skill adapted from jev-ultrafast that lets Codex hand multi-step Chrome tasks to Jev with preset inputs.

    Agent skillbetaPython
  • jev-browser-use

    Codex browser skill where Jev handles navigation, clicks, toggles and scrolling while Codex handles text input and verification.

    Agent skillbetaTypeScript
  • jev-browser-use

    Local browser automation workbench with an Edge/Chrome sidebar and Codex MCP sharing one Jev-driven task engine, with user confirmation.

    MCP serverbetaTypeScript
  • jev-max

    Jev browser agent that pierces shadow DOM and iframes, adds canvas fallback and full actions, with one Jev request per cycle.

    MCP serverbetaPython