Small decisions. Interesting possibilities.Submit contentSubmit
jev-browser-use preview

jev-browser-use

5–10x faster browser operations: Jev clicks, Codex thinks and verifies. Built at EZCollegeApp.

Added to Jevfast

How it uses Jev

The browser skill sends task goal, browser snapshot, and action history, then asks Jev for the next permitted action from observed controls. The bridge validates the answer and state before dispatching a browser action.

What Jev decides

Illustrative Jev decisionExample answers · not a recorded Jev response · Source ↗
Question 1 · next
YOUR APP
INSTRUCTION

Choose the next action that advances the goal from permitted observed controls.

STATE

Goal, browser accessibility snapshot, action history, and any permitted actions derived from observed controls. This example shows the three fixed options alongside those dynamic actions.

JEV · CHOICE
  1. DONE
  2. BLOCKED
  3. WAIT

App workflow

  1. Inspect browser

    Read a fresh accessibility snapshot and discover permitted controls.

  2. Build decision request

    Combine the goal, browser state, history, and policy-filtered action criteria.

  3. Ask Jev

    Request a Choice for the next action.

  4. Validate and execute

    Check the response and state version, then dispatch the selected browser action.

Why it is interesting

It packages browser operation as a reusable skill with provider configuration, bounded requests, and checks for stale state before acting.