Video wird geladen...
Video konnte nicht geladen werden
Python person here. Every time I tried browser automation on a site without an API, it died the moment the page layout changed. The Sai API clip is the opposite of that experience. The Muse app gets told to log in to Product Hunt with Google. You see its... show more
20,314 Aufrufe • vor 21 Tagen •via X (Twitter)
27 Kommentare

lfg sai 🚀

79.38% on OSWorld? impressive

reuse after one execution solves the token burn issue pretty nicely

reusing learned steps to cut API costs is huge for production scripts

what saved my scrapers: select by role and visible text, never css classes. the layout changes every week, the word "Submit" almost never does

Wait how does it handle CAPTCHAs on the Google login flow?

Was expecting another wrapper around selenium but the model-agnostic setup with Qwen is smart

big win for cursor users

up only 🔥

Always skeptical of 'no DOM selector' tools but passing raw visual intent to Claude actually worked on the demo

Thought browser automation without APIs was a dead end until I saw the Product Hunt sign-in clip

Ok the single vm per agent thing actually makes sense

what are latency costs like when DeepSeek is driving it?

OSWorld 2.0 top spot

lfg model-agnostic is the way 🚀

79.38% on OSWorld is wild ngl

i used to spend half my day fixing broken playwright selectors so this speaks to my soul

Browser automation that trusts the UI banner breaks on the first 5xx. @jshookmcp verifies at the CDP layer — did the write actually fire, did the DOM really mutate. Completion you can prove, not claim.

Windows cloud computer live tab

how does it handle 2FA when logging into google via that muse clip?

Wait, no selectors AND no VM to maintain?? That's the part every browser-agent demo conveniently skips. Honest question though — the model-agnostic claim: in your actual tests did Qwen/DeepSeek keep up with Claude at clicking the right things?

Does the learned action cache across different machines or just locally

Start with one repeated task on its own machine, then log where it fails before adding more agents; isolated runs make it easier to debug and reuse the workflow.

no VM maintenance overhead sounds almost too good to be true

Bye selenium selectors you wont be missed lol

codex support too nice

Honest question, what happens when google drops a CAPTCHA during that login flow?
