Jev Desktop plugin
A Codex plugin that speeds up Computer Use: short click and fill loops in the browser and macOS apps, with verification.
- 80 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The plugin clicks and types in the user browser and apps, and element labels go to an external service.
Install
- Works in
Manual install
codex plugin marketplace add yikangy873-gif/jev-desktopThen `codex plugin add jev-desktop@yikangy873-plugins` and key setup through `scripts/setup.py`.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The plugin clicks and types in the user browser and apps, and element labels go to an external service.
This is third-party code. Review the repository files before installing.
What it does
The plugin adds a bounded decision loop to Codex Computer Use. Codex sets the goal, prepares text, defines allowed actions and verifies the outcome, Computer Use reads the accessibility tree and performs the click, fill or scroll, and the TypeSafe Jev service picks an operation and a matching target in one request. Control does not return to the main agent after every click. It supports clicks on allowed buttons, links and tabs, filling fields from prepared `textSlots` values, scrolling and safe keyboard shortcuts. Sending, payment, deletion, file upload, login and permission changes are not done by the plugin: those steps return to Codex. The `jev-desktop` skill loads only in a new task.
Who it is for. Codex users with Computer Use who often run the agent through forms and pages and want less waiting between steps.
Good fit when
- In the current tab known data is filled in, preview is clicked and the result is checked.
- A set of filters is applied on a page and the run stops once the right results have loaded.
- Several independent form fields are filled in turn with screen freshness checks.
- A script walks through the menu of a macOS app that has an accessibility tree.
Not a fit when
- The task is sending a payment, deleting or publishing, which the plugin does not do.
- The interface is drawn on a canvas or exposes no accessibility tree.
- You need a general unrestricted desktop control agent.
Example request
Use Jev Desktop in the current browser tab: apply the filters from my list and stop when the results have loaded.Limitations
Codex with plugin support, Node.js 22 or newer, Python 3.10 or newer and a TypeSafe API key are required. The key is entered on a local page opened by `setup.py`, not in the Codex chat. The TypeSafe service receives the task goal and the labels and roles of allowed elements, while screenshots, the full accessibility tree and prepared values stay on the machine. An end-to-end speedup is not proven: Computer Use observation contributes most of the latency. Apps without useful accessibility may need the regular visual mode or a dedicated connector.
How to disable. Run `codex plugin list --json`, find the `jev-desktop` plugin and remove it with Codex tools. Revoke the TypeSafe key entered on the setup page in the service dashboard.
FAQ
How do I install Jev Desktop?
Add the repository as a marketplace with `codex plugin marketplace add yikangy873-gif/jev-desktop`, then `codex plugin add jev-desktop@yikangy873-plugins`. Then start a new task.
Where do I enter the TypeSafe key?
On the local page whose address `python3 scripts/setup.py` prints. Do not paste the key into the Codex chat.
How do I check the install?
Run `node scripts/doctor.mjs --live`. It reports whether the key is configured and the API reachable, and never prints the key.
What is sent to TypeSafe?
The task goal, labels and roles of allowed elements, the list of supported operations and boolean observations. Screenshots and prepared values stay local.
What if the plugin directory is not found?
The cache path depends on the Codex version. Run `codex plugin list --json` to see it.
Discussion
No questions or reviews yet.
Related
PluginsA Claude Code command set that finds jobs, fills application forms in Chrome and sends only the ones you approve.
A local bridge into the running Codex desktop app for macOS: scripts and agents call its tools through a CLI or an MCP server.
A local macOS CLI that lets an agent read the screen via OCR, click and type, with no cloud and no vision model
Open Computer Use
open-computer-use
An open MCP server for desktop control: the agent reads app state and clicks, types and scrolls on macOS, Linux and Windows
An agent fills fields and selects menu items in a local application, checking the screen before and after each action.
A Rust CLI for macOS: an agent reads any app's interface through the accessibility tree and clicks, types and scrolls by element refs, with no screenshots
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Jev Desktop (this card) | no | 80 | ||
| typesafe-computer-use | no | 1,300 | a standalone CLI for driving a Mac; Jev Desktop plugs into Codex own Computer Use | |
| jev-browser | no | key is optional | 134 | a Playwright browser MCP server for Claude; Jev Desktop works in Codex and over the accessibility tree of browser and macOS |
README in short
The README explains the decision loop diagram, the data boundary, installation and key setup, sample tasks, supported actions, tests and limitations. A troubleshooting section covers typical `doctor.mjs` failures.