Patterns: browser, computer use, voice and product UI

TL;DR Four patterns where the options are built by code from what is on screen and Jev only picks: next browser action (P12), site-exposed tools (P13), desktop/mobile/voice/form control (P14) and a classifier inside an interface element (P34). Text entry always needs a small LLM beside it. Community tier: official pages win conflicts.

How to read this

Fit is our verdict against Jev 1.13 jaggedness: known failure modes and System One Models: strong, workable (caveat named) or poor. Pattern IDs are permanent; the index of all patterns is Decision patterns from the community (with fit verdicts).

Browser, computer use & voice

P12 Next browser action from a code-built menu

• Decision which on-page control advances the task
• State the goal, ids and labels of the controls observed this step, the last result
• Ask Choice over candidate ids — "Which option in candidates advances goal?"
• Code resolve id → predefined action, execute, re-observe; a small LLM writes text args
• Fit strong — the menu is rebuilt each step, so nothing can be invented
• Map Cookbook: Function calling
• Seen @gregpr07 (Browser Use: flight search in ~7 s for $0.0039, new action space every step, small LLM only to type — author-reported), @decapostos, browser-use/jev-ultrafast

P13 Picking a site-exposed tool instead of a click

• Decision which of the page's declared tools to call next
• State task, available tool descriptions, previous results
• Ask Choice over tool names; a fast cheap LLM generates the arguments
• Code validate arguments against the tool schema before executing
• Fit strong — @0xidanlevin reports 49/49 tasks with WebMCP vs 25/49 on their click harness
• Map Cookbook: Function calling
• Seen @0xidanlevin, nekuda-ai/WindTunnel

P14 Desktop, mobile, voice and form control

• Decision which element to act on, what the phrase meant, which field to fill
• State OCR/accessibility elements with ids, the live transcript, values extracted elsewhere
• Ask Choice for intent and for target in one request; per field use | check | click | skip
• Code perception is a separate, fallible stage — Jev sees no pixels, extracts no values
• Fit workable — @trycua reports 83.6% for hosted Jev on forms vs 99.7% for their task-specific specialist
• Map Cookbook: Pre-parsed value extraction
• Seen @instantricecook, @trycua, awlevin/typesafe-computer-use

Inside the product UI

P34 Classifier inside an interface element

• Decision what label, level or yes/no each visible row, message or field gets, for a judgment the user names
• State one item's text per call; visible items batched and sent in parallel
• Ask Score, Choice or Noul per item. When the user types their own judgment ("Urgency" as a column heading), turn it into ONE narrow question, show it, let them edit it
• Code key stays on the server, never in the browser; cache by item + question, re-run when the item text changes; sort, filter and any math in code; low confidence shown in words, not colour alone
• Fit strong — many tiny independent judgments, no writing; @dabit3 reports ~100 ms per rating (author-reported)
• Map Speculative fan-out, Score questions, Confidence-gated routing
• Seen @dabit3 (predictive spreadsheet; intent-ranked launcher); design rules from Nate B. Jones, placement 4 of his four

Related

• Decision patterns from the community (with fit verdicts) — index of every pattern; Consult guide: could Jev help this project? — the consult procedure
• Patterns: agent internals, context and coding agents, Patterns: judging, search, documents, real-time and markets, Patterns: marketing, sales, GTM, content, support and ops — the other domain pages
• Repos: coding agents, orchestration, memory, browser and computer use, integrations — the browser and computer-use repos; Field reports: independent evaluations, critiques, open replicas — what independent testers measured
• Cookbook: Function calling, Speculative fan-out, Confidence-gated routing

Sources

Post and repo links are inline in each pattern's Seen line. Raw captures (raw/x/, raw/x-repos/) live in the private repo.