Could you share your prompt? We'll look into this one
No easy answers on this one unfortunately, lots of conversations ongoing on these - but our default stance has been to hand back control to the user in cases of captcha and have them solve these when they arise.
At current latency, there's a bunch of async automation usecases that one could use this for. For example: *Tedious to complete, easy to verify BPO: Filling out doctor licensing applications based on context from a web…
We can definitely make the docs more clear here but the model requires using the computer_use tool. If you have custom tools, you'll need to exclude predefined tools if they clash with our action space. See this…
Hey - I'm on the team that launched this. Please let me know if you have any questions!
Could you share your prompt? We'll look into this one
No easy answers on this one unfortunately, lots of conversations ongoing on these - but our default stance has been to hand back control to the user in cases of captcha and have them solve these when they arise.
At current latency, there's a bunch of async automation usecases that one could use this for. For example: *Tedious to complete, easy to verify BPO: Filling out doctor licensing applications based on context from a web…
We can definitely make the docs more clear here but the model requires using the computer_use tool. If you have custom tools, you'll need to exclude predefined tools if they clash with our action space. See this…
Hey - I'm on the team that launched this. Please let me know if you have any questions!