Agents: read the raw Markdown of this page, or start at llms.txt.
~/wiki/ideas
Builds: browser, computer use and interface
TL;DR 22 builds, plus names-only lines (sweeps of 2026-09-23 and 2026-09-24; split from Builds: coding agents, harnesses and orchestration on 2026-09-25). Code builds the menu from what is on screen, Jev picks, a small LLM types any text, and a separate question or code checks "done". The best evidence is two task suites with stated limits: jev-browser 40/42 live tasks and Jev for Chrome 13/17. Point these agents only at sites and accounts you may automate (AUP note on Patterns: browser, computer use, voice and product UI).
How to read. Builder reports = the builder's own numbers, one run on their own workload, unverified. Pattern IDs: P12-P14, P34 in Patterns: browser, computer use, voice and product UI; P01-P11 in Patterns: agent internals, context and coding agents; P17, P27 in Patterns: judging, search, documents, real-time and markets; P38 in Patterns: gates, simulation, personas and other shapes (P38+). Coding agents and orchestration: Builds: coding agents, harnesses and orchestration.
Browser, mobile and computer use
| Build | Jev decides | Builder reports | P |
|---|---|---|---|
| Hunch (u/HAR5HA_7663) | Accessibility snapshot → operation and element, one request; hands off to the outer LLM on low confidence, a stalled page or a risky click; success checked in code | 153 ms median vs 678 ms gpt-4o-mini, both 24/24; 4-step form 3.4 s; same input moves p ~0.05. Typed values never reach Jev | P12, P06 |
| Stagehand loop (@kylejeong) | Accessibility tree as state, actions as options; Stagehand executes | $0.001 for one task on a remote browser | P12 |
| Second-hand shopping (@AlanDaitch) | Playwright + Jev per listing: discard, bid, or message the seller | ~26 listings/min, 406 ms per decision, USD 0.00085 for the search. It placed bids: money needs a P03 gate | P12, P17 |
| jevcumber (Michael Poage) | Gherkin step → action kind, control, which quoted literal, submit or not, all picked from the live page | ~1 s per step; refuses below 0.6 (0.75 for page-sourced values); lockfile replays in CI with no API calls | P12 |
| agent-device QA (Mike Grabowski, Callstack) | Mobile accessibility snapshot → choice over press/fill/scroll/wait plus pass/fail/incomplete; text to type is baked into the option |
14 s run, $0.0023. systemOne + choice() matches JavaScript/TypeScript SDK quick contract: install, client, choice/score/noul, answers, errors (the page a builder reads) (verified) |
P14 |
| Screenshot-free computer use (@milindlabs) | On-device segmentation + OCR turn the screen into a text list; Jev picks what to click, in a loop | ~90 ms per decision | P14 |
| WeChat group bot (reviewed by @VersunPan) | Jev + DeepSeek over the Android accessibility tree, screenshot + local OCR fallback, last 10 messages | No numbers; warns WeChat can detect it and ban the account | P14 |
| Jev for Chrome (chy4pro) | MV3 port of jev-ultrafast in your own tab and profile: element table plus goal → operation and a target per operation in one request; two independent nouls (task achieved? stuck?) veto a DONE or BLOCKED under 50%; a small chat model types text. OpenRouter, TypeSafe or Cloudflare |
13/17 on the author's suite (seven rounds: 9 to 14 while bugs were fixed; tasks flip between runs). Misses: two text-model 429s, a headless error page, and one model decision error (arXiv: had the sort control and still opened a same-titled 2026 paper). A stale-DOM executor bug (old cards left under a re-sorted list) failed a task six rounds running. Unpacked install, no Web Store listing | P12, P04 |
| jev-browser (Ying-Kai Liao; not the jkudish repo of the same name) | An LLM names one outcome per step via MCP and passes any text; per round Jev picks element, action and value and flags done / error / irreversible; Playwright acts; low confidence returns ambiguous or likely_done to the LLM |
42 live tasks in 16 categories: 40/42, 0 false "done" (38/41 twice before fixes; RESULTS.md: 202 Jev calls, 286 ms average); ~300 ms per call, 2-4 calls per step; paused only before saucedemo's place-order button in ~200 rounds; page content for the LLM cut ~5x median (its estimate). Stated limits: ordered sub-goals in one step, counting ("add until 3"), checking a sort order | P12, P03 |
| Jev Social (socai) | Next read-only operation (search, open a post or profile, read comments, a TikTok download only when asked) from a menu rebuilt from earlier results; the socai CLI runs it in your real, logged-in Chrome; tried operations leave the menu | One recorded Instagram run: 4 source-linked records in 63.969 s; no benchmark published yet. Report prose by an LLM (default openai/gpt-4o-mini). Flag: it automates your logged-in Instagram, TikTok and LinkedIn sessions; platform terms may forbid that (and see the AUP note on Patterns: browser, computer use, voice and product UI) |
P12, P13 |
| Yappy (Mitosis Labs; closed, paid) | Mac computer-use agent: the front window as an accessibility table of controls (no screenshots) → one operation question and a target question per operation; a chat model types; hands off to the full agent below 0.25 confidence, after three no-op actions, or when a field value is unknown | Vendor's own single run (2026-09-18, one job-application form, n=1): 1m54s vs 13m14s and ~$0.24 vs ~$4.24 for a named competitor, whose time includes ~2m20s waiting on the user (research page); five Jev decisions, 275-690 ms each, $0.003 in total | P14, P06 |
| Jev-in-the-Loop (Tongyun1) | Codex plugin on jev-ultrafast: Codex plans and prepares the text to type; Jev picks action, target and input per step in local Chrome; stops at a handoff page (booking form) | Demos only, no numbers | P12 |
Also seen, names only (vetted 2026-09-24): jev-ego (jev-ultrafast's action space on the ego lite browser), JevBystander (Android accessibility service reading private WeChat chats; ships a debug-signed APK with a public keystore: do not install), and "Jev Use" (@Saccc_c: Codex plus Jev adding a Mac calendar event, reported smoother than Codex's own computer use at about the same token use, video only, unverified).
Interface elements
| Build | Jev decides | Builder reports | P |
|---|---|---|---|
| jev-skip (valentynkit) | Captions in 30 s segments, one choice each (sponsor, intro, content …) in one request; seek bar tinted by probability |
77% of crowd-marked sponsor seconds on 23 videos, 34 s false skips per hour, $0.0008 per video (gateway shim) | P34, P27 |
| X timeline labeler (@the_cyw) | Chrome extension labels each post clean, engagement bait, promo, secondhand or filler | $0.03 per 1,000 posts | P34, P16 |
| Text box that turns into a UI (@anishfn) | Turns what you type into an interface. How is not published (video only); Jev does not generate markup, so it most likely picks among prebuilt components and code renders them (inferred), as json-render's documented path (next row) does | Demo only, no numbers | P34, P01 |
| json-render + Jev (Vercel Labs; demo @ctatedev) | Generative UI by selection. Your app supplies atomic candidates (component, concrete props, state bindings, allowed actions); Jev picks which to include, their order and parent/slot; json-render emits a validated flat Spec for your own renderer. Batched: one evaluation selects root and components, a second arranges; edits (remove, move, replace) take further evaluations |
Post: "rendered in milliseconds", no numbers. Docs: experimental, unreleased (experimental_composeSpec, source build); via Vercel AI Gateway typesafe-ai/jev; defaults 32 evaluations, 32 elements, depth 8, 10 s per evaluation. Jev "cannot invent missing prose or data": every string is a prepared candidate. A finished spec is not a correct one; the docs say their confidence is not a quality threshold |
P34, P01 |
| Needle (@Saboo_Shubham_) | Semantic ⌘F in a Chrome extension (or React app): query plus the page's readable passages go to a local backend; one evaluation scores every passage and picks its strongest sentence (question types not stated); code highlights it in place. Kept at relevance ≥ 0.58 | "Super fast and near real-time" (author), no numbers. Caps 160 passages, 60,000 characters (~15k tokens, inside the 32k state budget, inferred), 2,200 per passage; every captured passage leaves the machine; no PDFs. Vercel AI Gateway key only, a TypeSafe key does not work. Apache-2.0 | P17, P34 |
| Colour palettes (@mattdesl) | Any phrase (an 80s disco mood, Mario, the blue screen of death) → a palette. How is not published (video only); Jev writes no free text, so code most likely offers the colours and Jev picks (inferred) | None; author: "very cheap and fast" | P34 |
| Emoji picker (@heystefan_) | As you type, the emojis that match rise from a pile (starting a band → instruments), per Berman's narration; the post is a video with a one-line caption | None | P34 |
| TypeSafe Typewriter (@stevekrouse, Val Town) | Live demo of judgments re-asked as you type (video only; what it asks is not in the post) | None in the post | P34 |
| jev-canvas (gaborishka) | Voice plus a pointing fingertip on a tldraw canvas: every partial or final transcript sends one request with 8-9 questions (is_command and complete nouls; action, shape, colour, target shape and place choices; a five-step size rubric); code extracts text spans and Jev picks one; thresholds in code. Via OpenRouter's alpha Decisions API |
~350 ms per spoken word (its description). Talk not aimed at the canvas scores is_command around 2%, so nothing happens: a wake gate (Patterns: gates, simulation, personas and other shapes (P38+) P38) |
P14, P38 |
| jev-asks-until-sure (mintannn; demo) | Twenty-questions game where confidence is the stopping rule: over 55% it commits, 28-45% it hedges, under 28% it refuses. One request per turn with up to 18 questions (persona, region, prefecture, age Choices; 8 trait Scores; 8 Nouls; next question); a coarse 8-region Choice is multiplied into the 47-prefecture one |
230-440 ms per turn (author). Thresholds are the author's; confidence is not a probability of being right (Confidence vs probability) |
P06, P34 |
Also seen, names only: TypeSafe AdBlock (the author calls it a toy: one noul per ad-shaped DOM node, removed at 0.70 or above; numbers are turned into words before sending).
Palettes and emoji are world-knowledge Choice demos: the answer comes from what the model already knows, not from state, which is where Jev is weaker (capability atlas, Builds: data, content and business). Offer named colours rather than hex codes (numbers, Jev 1.13 jaggedness: known failure modes; inferred). Matthew Berman's walkthrough of these builds, and his framing of the UI demos (Jev chooses from your component library, it does not write code): Press and third-party coverage.
What these builds teach when advising
- The menu is rebuilt each step, so nothing is invented. Every browser row offers ids from the live page; json-render and Needle offer prepared candidates; text to type comes from the caller or a small LLM.
- Check "done" separately. jev-browser and Jev for Chrome ask an independent "task achieved?" question; Hunch verifies in code; jev-browser returns
likely_doneandambiguousto the planning LLM rather than guessing. - Write the limits down. jev-browser names ordered sub-goals, counting and sort checks; Jev for Chrome lists one real decision error and a stale-DOM executor bug. Ask for the same before trusting a demo.
- Vendor numbers are n=1. Yappy's comparison is one run on one form, by the seller.
- Logged-in automation is a terms question. Jev Social, the WeChat bot and JevBystander act inside personal accounts; the platform may forbid it.
Related
- Patterns: browser, computer use, voice and product UI — P12-P14, P34 with fit verdicts and the AUP note
- Builds: coding agents, harnesses and orchestration, Builds: data, content and business, Builds: games, simulators, robots and devices — the other builds pages
- Repos: coding agents, orchestration, memory, browser and computer use, integrations — jev-ultrafast, typesafe-computer-use, mobile-jev and other first-week repos
Sources
Links are inline in each row; the raw captures (2026-09-23 to 2026-09-25) are listed in the frontmatter. Names-only lines rest on our 2026-09-24 vetting at source (docs/sweep/2026-09-24-awesome-jev/part1.md, part2.md) where no capture exists.