Small decisions. Interesting possibilities.Submit contentSubmit

How it uses Jev

Within Codex Computer Use, Jev selects an allowed operation and its compatible target in one scoped request using indexed accessibility elements and recent action descriptions. Codex supplies the goal and prepared text, while Computer Use performs the action and Codex independently verifies the result.

What Jev decides

Illustrative Jev requestExample answers · not a recorded Jev response · Source ↗
Question 1 · operation
YOUR APP
INSTRUCTION

Choose the next operation.

STATE

Goal “Fill the project, enable reminder, preview”; Test screen has a project field, reminder checkbox, preview button and result text.

JEV · CHOICE
  1. TYPE_TEXT
  2. CLICK
  3. DONE
  4. BLOCKED

App workflow

  1. Scope the task

    Codex defines the goal, allowed controls, and any prepared text values; deterministic actions can use a direct path.

  2. Observe and choose

    Computer Use observes the interface, then Jev selects an operation and compatible target from allowed indexed elements.

  3. Execute and verify

    Validate freshness and safety constraints, perform the action through Computer Use, observe again, and let Codex verify the outcome.

Why it is interesting

It keeps a bounded action session inside the existing Computer Use runtime, with explicit allowlists, freshness checks, and consequential actions returned to Codex for policy handling.