DEMO / RECORDING
Overview & result
Kai's browser skill pairs an isolated Playwright Chromium session with Jev for selecting actions in the page. The original post demonstrates finding related articles and job openings from Antigravity CLI and Codex; the later public repository supplies the standalone jb CLI and installation instructions.
From the original post
Combined Jev with Playwright-controlled Chrome to build jev-browser, a general browser automation skill.
Works across agents. Two demos in Antigravity CLI and Codex: finding related articles, then job openings on a site.
Both ran fast. This could handle many more browser tasks.
How Jev fits in the loop
- The jb CLI starts an isolated Playwright Chromium session for a specified URL and goal.
- Page state and recent actions are sent to the configured Jev provider to choose the next in-page action.
- The CLI applies the selected browser action and exposes session state and recorded artifacts.
How to reproduce
- Clone github.com/hqman/jev-browser-skill, install dependencies and Playwright Chromium as described in the README.
- Configure the default AI Gateway provider or the optional TypeSafe provider in ~/.jb/config.json or environment variables.
- Use the repository's jb-browser skill and ./bin/jb run command for a bounded browser goal; inspect the returned state and artifacts.
Why this build matters
Provides a concrete, inspectable browser skill for coding agents, with documented provider choices and security boundaries.
Limitations
- Requires Node.js 22.18+ and an installed Playwright Chromium browser.
- This is an independently maintained standalone CLI derived from the earlier Cline plugin; it is not installed as a Cline plugin or published as an npm package.
- The repository says allowedOrigins controls navigation, not every network request, and model-selected needs_review is not a guaranteed sensitive-action block.