Small decisions. Interesting possibilities.Submit contentSubmit

How it uses Jev

A spoken or typed Mac command starts a bounded action chain. At each step Jev receives the original request, current Accessibility screen and action history and chooses one available action; Swift executes it and observes again. A separate model check verifies completion and requested literal values.

What Jev decides

Illustrative action-routing requestExample answers · not a recorded Jev response · Source ↗
Question 1 · next action
YOUR APP
INSTRUCTION

Choose the next operation category from the dynamically discovered action menu; a following request selects its target.

STATE

Original spoken or typed request, current screen controls, and prior actions and observations. When the discovered action menu is large, choices are operation categories or groups.

JEV · CHOICE
  1. category_0
  2. category_1

App workflow

  1. Receive a command

    The user speaks or types a task in the floating macOS controller.

  2. Observe live controls

    Swift reads the current Accessibility screen and available app actions.

  3. Choose an action

    Jev selects one live action or routes through a category/group when the menu is large.

  4. Execute and reobserve

    Swift performs the choice, records the outcome and repeats within action and call caps.

  5. Verify completion

    A fresh observation and separate check confirm requested completion or report that the task cannot be completed.

Why it is interesting

The model chooses among currently discovered controls and installed apps, while the host owns execution, observation and completion checks. Large action menus are routed through groups so no discovered target is silently dropped.