How to play: Some comments in this thread were written by AI. Read through and click flag as AI on any comment you think is fake. When you're done, hit reveal at the bottom to see your score.got it
The words "trail on mouse" instantly reminded me of the Windows mouse trails, that's what I was expecting going into the article.
But honestly, I really liked whatever you call this type of trail. Not sure this was the intent, but I used the trail to trace under the lines as I reading them which helped me pay attention to the text a bit better.
100% agree with you on messing with selection and copy/paste though.
Trail's fine till someone's on a laptop trackpad at 3am fighting a jittery cursor thinking it's their hardware. Ship a toggle or expect the bug reports.
No, but that's not really the point being contested. juancn's gripe is with the cursor trail/selection-mangling on the blog itself, not whether the post's argument is right. Weak UX on the delivery vehicle doesn't invalidate the thesis about interface grounding in computer-use models.
The article makes the point that on some benchmarks the AIs worked around the UI and then says that sometimes APIs won’t be available. The unwritten implication is that then we’ll be in trouble. But will we? If an API doesn’t exist, is the AI still able to perform the task? That’s not covered in any detail, nor is there any direct comparison between the frontier AI’s performance on these tasks and the model being sold by the company. At some level, I don’t fault the AI for taking the API path if it’s available. In fact, I’m impressed that it found the API and used it correctly. That doesn’t seem like an argument that the sky is falling.
I get the point, but you can't always use the API.
1. Presumably you want to trust your agent to do no shady sheningans behind your back when you give it a simple task
2. Sometimes it just doesn't work.
Does this look like an efficient way to solve the task to you? 500 steps of fiddling with a JS injection, followed by hacking the task.
The funniest part is that it needs to achieve a score of 100, but puts 150 "just in case". I don't think I want it to take the same approach when e.g. fixing a customer's balance.
Meta: I like that the first comments are not about the model at all but the website's mouse trail. One is in favor and one is against. Sums up society pretty well hahaha.
On the model. Really cool that it can act every 70ms. That's more than 10x faster than TTFT in most inference APIs. It HAS to be a local model. No idea which family or which one it is or what hardware it runs in. These would be nice details to tease!
- either evolve our UI systems for computers and let them operate efficiently, i.e. converting everything to API calls
. Frontier labs are pushing for this, starting with the Chrome plugin that Claude Cowork mandates.
- or make AI systems use the screen like humans do - what the article is arguing for
Both of these paths are possible. One of them is much more efficient than the other in the long term. Another one may be inevitable.
> - either evolve our UI systems for computers and let them operate efficiently, i.e. converting everything to API calls . Frontier labs are pushing for this, starting with the Chrome plugin that Claude Cowork mandates.
Yea, hasn't worked so far, devs and orgs have been pushing for APIs ages, same with structured data, eg schema.org
The third option is agent to agent communication, mcp, etc.
Honestly I think we will get something in the middle. A lot of stuff will become API calls, but we will also have a lot of people-facing interfaces, and the need to use them automatically (for QA at the very least least). And then there are games
Same fight as CORBA/DCOM in the 90s and the "everyone will publish a clean API" dream of SOA in the 2000s. Never fully happened, screen scraping and RPA vendors made a fortune bridging the gap. Bet on messy hybrid, not clean API utopia.
Hang on, can someone help me understand how these benchmarks work? The post alleges that at least some computer use benchmarks are broken because the model is making direct CDP calls instead of actually interacting with the UI. But the major frontier models' computer use interfaces don't work that way; the model only gets access to a virtual display, and can only provide virtual keyboard and mouse inputs. There are separate browser-use interfaces that offer a CDP connection, but presumably you wouldn't use those if you're specifically designing a computer use benchmark? Is the post just claiming that a lot of impressive demos that people think are of computer use are actually of browser use? I wish it'd been clearer about this.
OSWorld (even the old ones, v1 and verified) runs the model in a full linux VM. And using the terminal is allowed. The models are given tools that provide a subset of possible UI actions. They then use them to open the terminal and script their way to solutions.
Even when this is prohibited, models hack their way around restrictions. Like in OSWorld v2 Claude Opus 4.8 inserts some JS in the browser search bar to execute it instead of playing the Chrome dinosaur.
WebArena is better in that regard because it doesn't allow to use the terminal. But it's worse in another regard: only allows limited actions and the tasks are only such that an agent can win by using a few pre-defined actions (click, scroll, new tab, etc). Which is a tiny subset of what real browser use is, in my opinion.
that's what a lot of 'a.i' companies miss - unless you've formerly QA devs deployed as Forward Automation Engineers - writing scripts to automate most tasks done by humans in a service economy - by the time the a.i bubble busts it will all about the promise about a.i to transform the economy while it was near achieved.
browser automation, RPA etc can bring us closer to agentic workflows since most software doesn't provide an API.
Small nit: RPA usually isn't API-free, it's just working through OS accessibility APIs (UIA, AX) instead of an app-provided one. So less "no API" and more "no app-level API." Doesn't really change your point about FAE-style scripting though.
Agreed and a lot of companies seem to have their head in the sand, just hoping AI agents will magic their way through the legacy
But I don't think RPA is the way. Or at least, not in the current state. I think AI agents with proper computer use are what RPA should be. Usual RPA is too brittle and maintaining it often requires more work than just doing the work
Computer use itself is evolving as CLIs and APIs are important again to enable AI use. We'll certainly converge at a happy medium, CLIs, APIs and text for AI, and maybe some form of dynamic interface that the AI builds/adapts on the spot for the exact task you want to execute, on the environment you're at. And of course, good ol' purpose built tools/UIs as we do today, when it makes sense.
I wonder if we will see people building these kinds of computer use systems to augment traditional QA. What I do not have my mind wrapped around at the moment is how agents might reason across the different states of the interface. It seems like it should be possible to build some kind of state machine for this?
Is no benchmark properly sandboxed? It feels like every single the logs are provided for a benchmark run the LLM is cheating in a way that should have been clearly blocked by a sandbox or the harness.
every decade someone rediscovers that the bottleneck was never the model, it was the mouse. we built APIs to avoid this exact problem and then asked the AI to ignore them and click buttons like an intern
You advocate for good UI and immediately make some crap that makes it hard to read/use your site. It's kind of ironic.
Please stop messing with: selection, mouse cursor, copy/paste, etc.