Skip to content
OpenAgentSkill
Browsing is open · Catalog captured 2026-11-21 · Automatic updates and account services are paused.
Browser & automation

jev-browser-use

Fast browser actions with TypeSafe Jev. Codex handles planning, text input, visual interpretation, and verification; Jev handles navigation, clicks, toggles, and scrolling through the existing Computer Use runtime. Claude Code installation is supported; browser integration is coming soon.

wy-coliney · Owner publication

Installation

Read the source and dependencies before running a command. Copying does not install or execute anything.

npx skills add https://github.com/wy-coliney/jev-browser-use/tree/f14b60e0ae1ee90cd73eb6650e30a666a84c021a/skills/jev-browser-use --skill "jev-browser-use"

About this skill


name: jev-browser-use description: Fast browser actions with TypeSafe Jev. Codex handles planning, text input, visual interpretation, and verification; Jev handles navigation, clicks, toggles, and scrolling through the existing Computer Use runtime. Claude Code installation is supported; browser integration is coming soon.

Jev browser operations

Installable through npx skills add in Codex, Claude Code, and other compatible Skill hosts. Browser execution is currently validated only in Codex with the required Computer Use runtime. Claude Code browser integration is coming soon; installation alone does not provide it. If the runtime is absent, report that requirement instead of substituting unrelated browser tools.

Use this as the default first route for browser verification. Run the decision/action loop inside cua_repl so the host model does not spend a turn on each click. This is a browser-plugin bridge, not a standalone browser driver or a replacement for Codex's judgment.

Responsibilities and limits

  • Codex owns the task, authorization, all text entry, graphical recognition, visual interpretation, sensitive actions, and final verification. Jev is a fast mechanical browser operator: it chooses among currently observed permitted navigation, click, toggle, scroll, reload, and bounded key actions. It never chats, types or writes content, recognizes screenshots, generates selectors, code, coordinates, URLs, or arbitrary text.
  • Use only the in-app browser or Google Chrome; never Edge. Follow the current browser tool's first-call rules and documentation. Use cua_repl for every UI action. Do not launch a separate Playwright/CDP driver.
  • The helper supports named clicks, bounded scrolling, safe navigation keys, reloads, persistent multi-chunk sessions, and deterministic state waits. Scrolling can target the page, a freshly resolved named AX container, or a coordinate supplied once by Codex after visual recognition; Jev never invents coordinates. The helper deliberately exposes no text-entry action. Codex enters text and then resumes the same Jev session. Native select APIs, frames, canvas, drag-and-drop, uploads, screenshots as model input, and native desktop apps are not implemented in the helper. Use Codex's CUA tools for those gaps and resume Jev rather than abandoning delegation.
  • Jev returns needs_verification, never a verified pass. Codex must independently check the requested result using fresh browser state and screenshots when appropriate. A successful scroll may leave AX text unchanged; the helper records effectNeedsVisualVerification and continues instead of falsely declaring no progress.

The intended scale boundary is action-heavy browser work. Keep navigation, expanding panels, clicking buttons, toggling controls, paging, and scrolling inside Jev's loop so Codex does not spend a model turn on each mechanical action. Hand control to Codex for text entry, visual or semantic judgment, unsupported widgets, consequential approval gates, and final verification.

Load the configured helper

Call loadConfig() and pass its result unchanged into createSession() or run() as shown below. The helper owns authentication, API requests, and response validation. Browser tasks must not select a provider, override the configured model, write their own API client, or change credential configuration unless the user requests that change.

The user configuration works across project directories. The helper reads the credential from its configured local file; do not print credentials, dotenv contents, or raw HTTP error bodies, and do not put them in pages or traces. A missing credential is a configuration problem: do not search unrelated files or silently switch providers.

Only for installation, provider changes, or API troubleshooting, read API integration maintenance. It documents all currently supported adapters. It is not required reading for browser verification.

Discover the browser tool correctly — required before declaring it unavailable

cua_repl is normally a direct tool namespace, exposed as mcp__cua_repl.js and mcp__cua_repl.js_reset. It is not a nested tools.* method inside functions.exec. The app-managed plugin intentionally omits these tools from code-mode and deferred tool lists. Therefore an empty ALL_TOOLS.filter(... /cua|browser/ ...) result does not show that the browser plugin is missing. Do not repeatedly search that list or stop on that basis.

  1. Inspect the direct tool declarations available in this turn before searching generic tool catalogs. Prefer mcp__cua_repl.js when present. Use its documented first-call entry point and read the returned runtime documentation before continuing. Never invent a tool name or route a direct tool through shell, HTTP, or a guessed tools.* method.
  2. If that exact namespace is absent, inspect other declared browser/computer-use tools and any available discovery mechanism once. Follow their own documented entry points. A different tool name is not proof of incompatibility, but this bridge still requires a compatible tab API and module-import runtime. Verify those capabilities before importing it. If only host browser controls are available, use them within the user's scope and report that Jev delegation was unavailable; do not claim the bridge worked or improvise an untested adapter.
  3. Keep three states separate: plugin enabled globally, tool exposed to this turn, and requested browser/profile/tab reachable. Configuration proves only enablement. A plugin mention proves only selection. A successful documented read of the requested tab proves reachability. A blank in-app tab does not establish access to the user's Chrome session.
  4. If the user named Chrome or an existing tab, use the runtime's documented discovery/attachment API for that target. Do not open a replacement browser session or claim
Read the complete source ↗