Jev Browser Wingman
github.com/coderexpert123/jev-browser-wingman- Category
- AI Agents
- Rank
- No. 3926Tools index
Previous survey · No. 3707 ·
- Pricing
- Open Source
- Type
- TOOL
- Use case
- Workflow Automation
- GitHub
- 7 stars
- Latest release
- v0.4.2
- Date
About
A browser automation tool in which TypeSafe's Jev model chooses each step. It attaches to an existing Chrome instance over the Chrome DevTools Protocol and can run alongside Playwright MCP, so an agent can hand browser actions to Jev. It is not affiliated with TypeSafe.
At a glance
Jev Browser Wingman uses TypeSafe to choose which visible page element an agent should click or type into, then performs the action in the browser. It is worth evaluating on public test pages if your browser agent often picks the wrong control.
Good fit
Developers comparing browser automation on synthetic pages with ambiguous buttons or forms.
Consider something else when
Skip it if page text, URLs or task descriptions must stay on your machine. The documented default sends excerpts even from sensitive pages.
Start here
Use an unsigned-in, disposable browser profile with a synthetic form. Set policy.mode to enforce before testing. Give the agent a page with two similarly named buttons and check which element it selects.
Cost and requirements
The documented setup requires a TypeSafe API key, a compatible agent and a browser. Check TypeSafe’s current usage terms before sending traffic.
Limits to know
The publisher says typed values stay local, while page text, URL paths and goal descriptions can go to TypeSafe. The optional enforcement mode detects some sensitive pages and adds an action gate. Treat the trial as public-data only.
Sources checked 2026-11-05. Source-based assessment.
Tags
Tech Stack
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.