| ▲ | euphetar 2 hours ago | ||||||||||||||||
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. https://osworld-v2-monitor.xlang.ai/task/tasks/068 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. | |||||||||||||||||
| ▲ | drob518 2 hours ago | parent [-] | ||||||||||||||||
Well, there’s a bigger issue of AIs not doing what we tell them to do, but I think that’s orthogonal to this UI issue. If you want to fault the model for not obeying the prompt or for a poor solution, then fine. My point is, it solved the problem. If the API isn’t there, then that eliminates the API as a solution, but it says nothing about how well the model can solve the UI problem. Perhaps the model can’t solve it. If we really want to benchmark the ability of models to use human UIs to solve problems, then perhaps we need to choose benchmarks that don’t have APIs available such that the model cannot get “creative” in any way and must use the UI as part of the task. More simply, maybe the model isn’t the problem; maybe the benchmark designer is. | |||||||||||||||||
| |||||||||||||||||