Skip to content

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 serverbeta

Overview

Jev Browser Use by except-100 is a local browser automation workbench, documented in Chinese, in which a Chrome or Edge sidebar extension and a Codex MCP server share the same task engine, policies, SQLite records, workflows and results. The browser is driven by the extension through chrome.debugger and CDP, and Jev makes the main decisions. Users enter a web goal, Jev executes it, key actions require user confirmation, and users can pause or take over at any time.

Version 0.2.0 added step-by-step goal evaluation, automatic recovery during normal browsing, evidence kept across pages, and sourced Markdown reports; real-model runs completed search and reading tasks on GitHub, Python docs and MDN, with failures and retests recorded, though the README notes these do not mean any site will work. The server binds only to 127.0.0.1, uses one-time pairing codes valid for 10 minutes, and blocks web origins from the task API. It requires Node 24.21 and pnpm 11.18, with Windows as the primary test platform, and offers a labelled simulation mode for demos.

What the decision model decides

TypeQuestionAnswers
ChoiceWhich page action advances the goal?(inferred)—
Yes / noHas this step's goal been achieved?(inferred)yes · no

How it works

  1. Start the local server and pair the sidebar extension
  2. Enter a goal in the sidebar or via Codex MCP
  3. Jev decides actions; key actions await user confirmation
  4. Evaluate each step; recover and keep evidence
  5. Produce a sourced Markdown report

Strengths

  • Human confirmation for key actions
  • Shared engine for sidebar and Codex
  • Local-only server with pairing

Caveats

  • Pinned Node and pnpm versions; Windows-first testing
  • Documentation in Chinese

Getting started

`pnpm install --frozen-lockfile && pnpm build && pnpm start`, load the extension unpacked, and pair with the code shown.

At a glance

Type
MCP server
Status
beta
Language
TypeScript
Runtime
browser extension, local server, MCP
Has code
yes

Use cases and integrations

How curated lists describe it

Frequently asked questions

What does Jev decide?

The main browser actions and whether each step's goal is met.

Can I stop it?

Yes, key actions need confirmation and you can pause or take over at any time.

Is there a demo mode?

Yes, a clearly labelled simulation mode.

Related projects

  • 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
  • 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
  • Chinese-language Codex skill adapted from jev-ultrafast that lets Codex hand multi-step Chrome tasks to Jev with preset inputs.

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

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

    MCP serverbetaPython
  • MCP server that lets Claude Code or Codex drive real Chrome with Jev picking elements and checking steps, plus safety gates and traces.

    MCP serverbetaTypeScript