Computer use with Jev

You stay the planner and the hands. Jev is only the fast "which one next?" in the middle. It returns an id from a table you built, so it cannot invent coordinates, text, selectors or tool calls. The worst a wrong answer can do is pick another action you already judged safe.

Web pages belong to jev-browser-use. This skill is for desktop apps and OS surfaces, driven through whatever computer-use driver you have (CUA Driver over MCP, the platform's native computer-use tool, an accessibility bridge).

First choice on a Mac: Co-Agent does the loop for you

If Co-Agent is installed (its engine answers on http://127.0.0.1:8792), let it drive. It already holds the Mac's Accessibility and Screen Recording permissions, runs this same loop natively (fresh observation, Jev picks one id from a closed menu, one action, a new observation to verify) and adds what hand-built loops kept getting wrong:

• it hit-tests every click and brings a covered window forward (or refuses with occluded), instead of clicking whatever app is really on top;
• it reads apps with no accessibility tree (Epic Games Launcher, games, canvases) with on-device OCR, and clicks them in a way Unreal and WebKit accept;
• it applies the owner's policy per action with no dialog for ordinary input, and answers needs_approval with a ticket at once for purchases, deleting, sending, legal acceptance, sign-in and security settings; it never types credentials;
• it names a lock screen or a macOS permission prompt as blocked instead of hanging.

Agents with MCP use its tools computer_status, computer_observe, computer_act and computer_run. Agents that shell out use the bundled client: