Jev Desktop for Codex

That is not demonstrated yet, and the 0.2.0 notes say so directly: it does not prove an end-to-end speedup because the previous runner already used one TypeSafe request per action, and Computer Use observation remains the main latency source in the measured samples. The browser integration was exercised end to end against the real API, but the README calls those integration samples, not a controlled comparison.

No. Every executable control has to be explicitly allowed by the calling Codex task, and consequential controls (send, publish, payment, deletion, upload, login, installation, permission changes) return to Codex for the applicable user-authorization policy instead of running in the fast loop. The loop likewise hands back DONE, BLOCKED, low-confidence, stale-state, and policy-sensitive outcomes instead of guessing.

Only what you prepared. TYPE_TEXT selects a caller-prepared slot rather than invoking another text model, and prepared field values stay local: the full accessibility tree, screenshots, the values themselves, and the CUA target objects never leave the machine. What goes to TypeSafe is the scoped task goal, allowed indexed element labels and roles, the supported operations, and filled-slot identifiers.

It targets browser tabs and native macOS apps through the existing Computer Use runtime, but the README is blunt about the gaps: apps without useful accessibility information may need visual Computer Use or a dedicated connector, and canvas interfaces, arbitrary native menus, and inaccessible custom widgets are not automatically supported. Element-index freshness checks are also not equivalent to DOM-node identity or occlusion checks.

Codex desktop or CLI with plugin support, Node.js 22 or newer, Python 3.10 or newer and a TypeSafe API key. Add the marketplace with `codex plugin marketplace add yikangy873-gif/jev-desktop` and install with `codex plugin add jev-desktop@yikangy873-plugins`.

The key is entered through a local loopback setup page, not pasted into a Codex chat, and the node bridge holds it. The accessibility tree, screenshots and prepared field values stay local; only the scoped task goal, allowed element labels and roles, supported operations, boolean observations and recent action descriptions go to TypeSafe.

MIT. The README calls it an original Codex adaptation that builds on browser-use/jev-ultrafast's operation and target-head policy and Cline's bounded reused-session approach, rather than a drop-in copy of either project.