Operator research preview
21–30 of 448 posts
Re: Operator research preview
#22"[Operator safety risks and mitigations] Harmful tasks: User is misaligned"
Looking forward to seeing some more of the examples for when openai considers their users as "misaligned", whatever that actually even means anymore.
Re: Operator research preview
#23> We’re collaborating with companies like DoorDash, Instacart, OpenTable, Priceline, StubHub, Thumbtack, Uber, and others to ensure Operator addresses real-world needs while respecting established norms. If you're collaborating with the companies the agent is supposed to interact with, why not just have it hook into an API rather than jumping through hoops to interface with their GUI? I don't get it.
Re: Operator research preview
#24Re: Operator research preview
#25Waiting for the "OpenAI has no moat" crowd to chime in while they keep releasing new features and dominating market share. (And yeah, they just got half a trillion ). Edit: Downvote all you want, reality won't change. Oh, what happened with "Scarlett Johansson will take down OpenAI because she invented speaking like a woman", literally nothing. What about "AI will never replace Hollywood actors". What about that time…
Re: Operator research preview
#26Re: Operator research preview
#27Overall, Operator seems the same as Claude's Computer Use demo from a few months ago, including architecture requiring user to launch a VM, and a tendency to be incorrect: https://news.ycombinator.com/item?id=41914989 Notably, Claude's Computer Use implementation made few waves in the AI Agent industry since that announcement despite the hype.
So the workflow for the human is ask the AI to do several things, then in the meantime between issuing new instructions, look at paused AI operator/agent flows stemming from prior instructions and unblock/approve them.
Like a general instructing an army.
Re: Operator research preview
#28> We’re collaborating with companies like DoorDash, Instacart, OpenTable, Priceline, StubHub, Thumbtack, Uber, and others to ensure Operator addresses real-world needs while respecting established norms. If you're collaborating with the companies the agent is supposed to interact with, why not just have it hook into an API rather than jumping through hoops to interface with their GUI? I don't get it.
The point is to move beyond APIs. Being able to perform actions on a site, with the ability to perform the task successfully even if the site slightly changes under the hood, is a lot less brittle than interacting with an API.
Re: Operator research preview
#29Waiting for the "OpenAI has no moat" crowd to chime in while they keep releasing new features and dominating market share. (And yeah, they just got half a trillion ). Edit: Downvote all you want, reality won't change. Oh, what happened with "Scarlett Johansson will take down OpenAI because she invented speaking like a woman", literally nothing. What about "AI will never replace Hollywood actors". What about that time…
Re: Operator research preview
#30Waiting for the "OpenAI has no moat" crowd to chime in while they keep releasing new features and dominating market share. (And yeah, they just got half a trillion ). Edit: Downvote all you want, reality won't change. Oh, what happened with "Scarlett Johansson will take down OpenAI because she invented speaking like a woman", literally nothing. What about "AI will never replace Hollywood actors". What about that time…