Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Operator research preview

openai.com

Post reply on HN
Print view View original

51–60 of 448 posts

Re: Operator research preview

#51

Post by moralestapia »

kristofferR wrote: post #16
moralestapia wrote: post #11

Waiting 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…

From what they've shown so far, this is just an old Anthropic feature. They haven't got half a trillion either, look up more details. It's a wish they have, funding right now amounts to around $100 billion

[flagged]

Re: Operator research preview

#52

Post by achierius »

usaar333 wrote: post #34
minimaxir wrote: post #8

Overall, 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.

38% on osworld vs 22% for Claude. That seems like a jump

But of course, after all the benchmark issues we've had thus far -- memorization, conflicts of interest, and just plainly low-quality questions -- I think it's fair to be suspicious of the extent to which these numbers will actually map to usability in the real world.

Re: Operator research preview

#54

Post by brap »

kccqzy wrote: post #45
brap wrote: post #31

I don't know why, but the approach where "agents" accomplish things by using a mouse and keyboard and looking at pixels always seemed off to me. I understand that in theory it's more flexible, but I always imagined some sort of standard, where apps and services can expose a set of pre-approved actions on the user's behalf. And the user can add/revoke privileges from agents at any point. Kind of like OAuth scopes. Ima…

If there are pre-approved standardized actions, it would be just be a plain old API; it would not be AGI. It's clear the AI companies are aiming for general computer use, not just coding against pre-approved APIs.

Naturally a "capability" is really just API + prompt.

If your product has a well documented OpenAPI endpoint (not to be confused with OpenAI), then you're basically done as a developer. Just add that endpoint to the "app store", choose your logo, and add your bank account for $$.

Re: Operator research preview

#56

Post by refulgentis »

hammock wrote: post #17
Mond_ wrote: post #7

I wonder, did Google or Microsoft (via Github Copilot) release anything like this yet? I'd not be surprised if all of them are currently working on something in this direction. "Agents", or something like that.

Google has had a similar, agentic feature on Pixel phones since 2018. (Back when people used to speak on the phone rather than do everything thru an app) https://research.google/blog/google-duplex-an-ai-system-for-...

Not quite. This is operating a computer, Duplex is a (very small) set of pre canned WAVs that can handle negotiating a time during a phone call

Re: Operator research preview

#57

Post by thrtythreeforty »

brap wrote: post #31

I don't know why, but the approach where "agents" accomplish things by using a mouse and keyboard and looking at pixels always seemed off to me. I understand that in theory it's more flexible, but I always imagined some sort of standard, where apps and services can expose a set of pre-approved actions on the user's behalf. And the user can add/revoke privileges from agents at any point. Kind of like OAuth scopes. Ima…

APIs have an MxN problem. N tools each need to implement M different APIs.

In nearly every case (that an end user cares about), an API will also have a GUI frontend. The GUI is discoverable, able to be authenticated against, definitely exists, and generally usable by the lowest common denominator. Teaching the AI to use this generically, solves the same problem as implementing support for a bunch of APIs without the discoverability and existence problems. In many ways this is horrific compute waste, but it's also a generic MxN solution.

Re: Operator research preview

#58

Post by madeofpalk »

tedsanders wrote: post #33
easterncalculus wrote: post #22

From the slide deck on the livestream: "[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.

I assume here it means complying with requests that could harm other people. It's pretty common for businesses to tell their employees not to assist customers doing bad things, so not surprised to see AIs trained to not to assist customers doing bad things. Examples: - "operator, please sign up for 100 fake Reddit accounts and have them regularly make posts praising product X." - "operator, please order the component…

"operator, please perform this computationally expensive action on my competitors website 1000000 times"

Re: Operator research preview

#59

Post by hammock »

tedsanders wrote: post #33
easterncalculus wrote: post #22

From the slide deck on the livestream: "[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.

I assume here it means complying with requests that could harm other people. It's pretty common for businesses to tell their employees not to assist customers doing bad things, so not surprised to see AIs trained to not to assist customers doing bad things. Examples: - "operator, please sign up for 100 fake Reddit accounts and have them regularly make posts praising product X." - "operator, please order the component…

Isn't that reddit/home depot/instagram's problem? Not a job for the guy you hired to do a thing

Re: Operator research preview

#60

Post by bko »

minimaxir wrote: post #8

Overall, 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.

I thought Claude Computer Use is through API, and I remember hearing about high number of queries and charges.

This looks like its in browser through the standard $20 Pro fee, which is huge. (EDIT: $200 a month plan so less of a slam dunk but still might be worth it)

Is there any open source or cheap ways to automate things on your computer? For instance I was thinking about a workflow like:

1. Use web to search for [companies] with conditions

2. Use linked in sales navigator to identify people in specific companies and loose search on job title or summary / experience

3. Collect the names for review

Or linked in only: Look at leads provided, and identify any companies they had worked for previously and find similar people in that job title

It doesn't have to be computer use, but given that it relies on my LinkedIn login, it would have to be.

Post reply on HN