jev-ultrafast
One request picks both the operation and the target element from an indexed DOM table; a small LLM only writes typed text. Zürich to London booked in 7.1 seconds.
Home / Browser and computer use
17 entries
One request picks both the operation and the target element from an indexed DOM table; a small LLM only writes typed text. Zürich to London booked in 7.1 seconds.
The same loop on a real Android phone; nine Uber actions in 21 seconds in the demo.
The first community browser agent on Jev, with a demo GIF.
Browser agent that spends one Jev request per step to pick the action.
Codex skill and plugin where Jev handles navigation, clicks, and scrolling and Codex keeps typing and verification; reports browser steps 5 to 10 times faster.
Job-hunting skill that drives Chrome over CDP and has Jev score every link and listing.
Lets Jev choose each read-only social research step while socai runs it in a real Chrome session and streams inspectable Instagram, TikTok, or LinkedIn evidence into a report.
Runs browser tasks from a plain-language instruction over CDP or Vercel's agent-browser, with Jev selecting operations and targets and code checking confidence before it acts.
OCR the screen, classify the next action, click; about $0.0002 a step on macOS.
Voice and typed computer use for macOS: Jev picks the next on-screen action from the Accessibility tree, with no screenshots.
Runs a delegated GUI task for Codex through the real Chrome session or Windows UI Automation, with Jev picking the control at each step.
An LLM plans, Jev decides; library, CLI, and MCP server.
One grounded Jev and Playwright core behind a typed SDK, a persistent CLI, and an MCP server.
Android sub-agent over USB running observe, normalize, decide, mutate, verify, with Jev deciding.
Android automation where one Jev request picks both the action and the target element from the accessibility tree, executed over ADB.
Codex computer use where Jev picks the element, action, completion, and risk from on-screen text, no screenshots sent; Chinese readme.
Intent and target decided per spoken word in about 300 ms, often before the sentence ends.