Small decisions. Interesting possibilities.Submit contentSubmit

How it uses Jev

Flick sends Jev a compact state of the user goal, supplied inputs, success conditions, optional task plan and artifacts, current interface observation, available apps, memory, and recent action effects. Jev chooses a typed operation from the currently available candidates; for most operations it also chooses an observed target. Filling requires separate target and supplied-value choices, so Jev selects text supplied or remembered by the user rather than inventing field contents.

What Jev decides

Choose the next available computer-use operationExample answers · not a recorded Jev response · Source ↗
Question 1 · operation
YOUR APP
INSTRUCTION

Choose among action groups available for this observation; the set changes with the visible controls and candidate actions.

STATE

The state includes goal, supplied_inputs, success_conditions, optional task_state {active_objective, plan, artifacts}, optional app_guides, now {iso, local, timezone}, interface {title, url, target, OCR status, optional tabs/loading/scroll/open_layer, text, observed elements, more_controls_not_listed}, optional clipboard, available_apps, optional memory, and recent_actions_and_effects (last 8). A separate completion verifier later asks a Noul question; this chart is only the action-selection request.

JEV · CHOICE
  1. click
  2. right_click
  3. double_click
  4. fill
  5. compose
  6. draft
  7. copy_text
  8. switch_tab
  9. fill_submit
  10. select
  11. press
  12. scroll
  13. wait
  14. scroll_top
  15. scroll_bottom
  16. wait_for_load
  17. wait_for_change
  18. wait_for_images
  19. scan_screen
  20. inspect_more
  21. request_vision
  22. complete_milestone
  23. modify_plan
  24. back
  25. forward
  26. refresh
  27. switch
  28. remember
  29. emergency_stop
  30. done
  31. blocked

App workflow

  1. Describe the task and constraints

    The host gives Flick the goal, supplied input values, and completion conditions. Flick observes the foreground interface and maintains task state, milestones, and retained artifacts.

  2. Select and execute an action

    The TypeSafe decider offers only actions available from the current observation. Jev chooses the operation and a matching target; fill decisions also pair an observed field with an exact supplied or remembered value. Flick executes the choice and observes the result.

  3. Repeat and verify

    The controller repeats while the task progresses. Jev separately judges evidence for milestone completion and final coverage of the user goal; the host returns the task status and collected evidence.

Why it is interesting

The integration factors computer use into auditable decisions over live, observed choices. It couples operation selection to a matching target question, keeps fill values constrained to user-provided or remembered text, and uses separate Jev judgments to assess milestone evidence and whole-goal completion.