jev-browser-wingman 0.3.0 — forced handoff

jev-browser-wingman 0.3.0

jev-browser-wingman (wingman for short) hands your AI agent's browser clicks and typing to TypeSafe's Jev. Jev chooses which element each step acts on, handing the step back when unsure, and wingman carries out the action in your real, logged-in browser. The agent keeps planning and sends its page work to one tool, browse_step.

Headline numbers

We ran 17 small browser tasks, such as ticking a checkbox or checking out in a demo shop. Each ran twice with wingman and twice with Playwright alone, in alternating order: 68 runs. "Playwright alone" means the same agent using the regular Playwright MCP browser tools (MCP is how agents talk to tool servers). The agent was the same in both setups.

• Completion: wingman completed all 34 runs. Playwright alone completed 32 of 34. Both misses were the file-upload task.
• Cost: the median run cost $0.162 against $0.177, about 9% lower. Total spend over all 34 runs was $4.86 against $5.40, 10% lower. Wingman was cheaper on 13 of 17 tasks. Costs are token use at list prices, not billing.
• Speed: the median run took 13.1 s against 11.7 s, so wingman was 1.4 s slower on the median. It was faster on file upload, infinite scroll, table sort, double-click and checkboxes. It was slower by 4 s or more on the start-loading task (wait for hidden text; 41.9 s against 20.5 s), the seven-page task (50.4 s against 34.0 s), the todo app, the confirm dialog and the demo-shop checkout.

With two runs per task, read the differences as indicative, not statistically established.

How it works

Wingman sits in front of your existing browser tool (an MCP server such as Playwright MCP). It hides that tool's page-action tools and keeps reading, tabs, dialogs and a few others. For each step that needs an element, it asks Jev which one to act on. Then it acts, checks the result and returns. If it is unsure, it hands that step back to the agent.

What is in this release

• Hand-off mode, where wingman hides the agent's own action tools, is the default: clicks, typing, selecting, key presses, hovering, uploads and navigation go through browse_step.
• One call runs up to 12 steps and returns progress you can resume.
• If a step's action already ran but the page then failed to settle, wingman says so. It tells the agent not to repeat the action and to continue with only the later steps.

Install

npm install -g jev-browser-wingman
jev-browser-wingman doctor --plan

The plan lists the exact setup your stack still needs. Needs Node.js 22+ and a TypeSafe API key.

Limits

No iframe or shadow-DOM content. Right-click, modifier-clicks and unusual keys need the agent's own script tool, which you keep with the handoff.retain setting. Browser tools that work only through a browser extension cannot share the browser. The benchmark results file is not in the repo.