Sac-Y / Jev-cu
“Hand Computer Use's next click to Jev (TypeSafe System One): Jev picks the element, action, completion, and risk from on-screen text candidates. Codex Computer Use reads and acts. Text only, no screenshots.”
Jev-Based rank #5In Harness #4
- 520Stars
- —Stars Δ / 1d
- —Stars Δ / 7d
- —Stars Δ / 30d
- 51Forks
- 2Watchers
GitHub ↗Official docs ↗Back to ranking
TL;DR
Sac-Y/Jev-cu showed up as Jev / System One related work: Codex Computer Use harness: Jev picks the next UI element and action from text candidates only.
The author describes it as: “Hand Computer Use’s next click to Jev (TypeSafe System One): Jev picks the element, action, completion, and risk from on-screen text candidates. Codex Computer Use reads and acts. Text only, no screenshots.” That is their claim, not a bench this site ran.
Who it’s for
- Agent / harness authors who need a typed gate, route, or prune step
- Computer-use and browser-loop authors who already have text state from OCR or the a11y tree
- Anyone who needs the unofficial line: jev.pro does not issue keys and is not TypeSafe
What’s inside
Top-level entries on GitHub at generation time: .env.example, .gitignore, README.md, fixtures, package-lock.json, package.json, scripts, skill, tests. Read those before you trust a one-line install.
How to use
- Clone and follow the author’s JavaScript toolchain. Do not invent a package name.
git clone https://github.com/Sac-Y/Jev-cu.git
cd Jev-cu
- If the project calls hosted Jev, you still need a TypeSafe console key or a documented gateway.
- Send a complete
stateand typed questions. Code owns control flow after the probabilities.
Hosted Jev still looks like a function call — wrapper or not:
{
model: "jev-1.13.0",
state: { source: "Sac-Y/Jev-cu", brief: "..." },
questions: {
gate: { type: "noul", instructions: "Should we act on this state?" },
route: { type: "choice", instructions: "Pick one next system.", criteria: ["code", "review", "human"] },
},
}
Try this
One typed action per frame
Using Sac-Y/Jev-cu, send Jev a text brief of the current screen and ask for Choice{click, type, wait, give_up}. Do not ask Jev for coordinates or screenshots — it is text-only.
Schema-safe ≠ correct
On a case Sac-Y/Jev-cu gets wrong, write down the schema-legal answer it returned and the human label. Do not “fix” it by asking Jev to generate an explanation.
FAQ
Does this replace the TypeSafe SDK?
Only if the author implemented a full client. Most harnesses still call the vendor SDK or raw HTTP.
Are the star chips live?
Star, fork, and watcher chips refresh from the public GitHub API via a scheduled job. The prose on this page is editorial.
Sources
Public repository metadata and TypeSafe documentation. No private claims.