GitHub · Browser agents
Sac-Y/Jev-cu
The clearest statement of a privacy and risk constraint inside the loop.
What it does
Hands "where do I click next" to Jev while Codex does the reading and the clicking. Jev chooses the element, the action, an estimate of completion and a risk level from text candidates only — screenshots are never sent — and a local policy gate blocks sensitive actions before they run.
The repository's own description: “No description published.”
How it works
`skill/jev-cu/` is installed into Codex (the install script rewrites a path placeholder), `scripts/` holds the Jev call, the policy gate, the decision loop and an offline evaluation, and `fixtures/` carries accessibility snapshots and P0 cases. The loop runs inside Codex's computer-use runtime.
The repository, by the numbers
Read from the GitHub API on 2026-09-22. Stars and the last push move daily — quote them with the date, the way we do.
What we checked
- the tree: fixtures, scripts, skill/jev-cu, tests
- MIT LICENSE (Sac-Y) and a package.json with install-skill/uninstall-skill scripts
- the README states text-only: no screenshots are sent
- the README describes the local policy gate and the offline evaluation directory
What we did not check. We did not install the skill or run the loop; the README is in Chinese and we read it in the original.