Loading lesson…
Operator points an agent at a real browser and lets it click, type, and navigate. The pattern is powerful and the failure modes are different from chat — supervision is not optional.
Operator is OpenAI's pattern for letting a model drive a real browser — clicking, typing, scrolling, filling forms. From the agent's perspective, the web is the UI. From your perspective, you are watching it work and stepping in when it loses the plot. The mental model is 'I am pair-driving with a junior assistant who has never seen this site before.'
| Task | Operator fit | Why |
|---|---|---|
| Find five vendors' shipping prices for a part | Strong | Read-only, repetitive, deterministic |
| Book a flight on a fare site | Risky | Real money, payment forms, anti-bot challenges |
| Update profile fields across three SaaS apps | OK with supervision | Stable forms but each click matters |
| Do my online banking | No | Credentials, money movement, terms-of-service |
| Fill out a job application | OK with heavy supervision | Mistakes are visible to the receiver |
The big idea: agentic browsing is real and useful, but it is a supervised tool. The day you stop watching is the day it does something you did not want.
15 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-openai-operator-creators
What mental model does the lesson suggest for thinking about how Operator works?
Which of the following is described as a STRONG fit for Operator?
What does the lesson say about using Operator on websites with frequently changing layouts?
What is a prompt injection risk when using Operator?
The lesson describes two 'rails' of approval for Operator. What are they?
Which defensive practice does the lesson recommend?
What should you do if you observe Operator getting stuck in a loop while running?
Why does the lesson compare Operator to a learner driver?
What type of task does the lesson say is 'OK with heavy supervision' for Operator?
What does the lesson recommend saving after running Operator on a task?
Why are anti-bot challenges listed as a weakness for Operator?
For the applied exercise, what should you evaluate after running Operator on a low-stakes task?
What does the lesson say about sites with heavy JavaScript modal flows?
The lesson mentions that early Operator testers reported the agent often behaves like what?
What kind of information should you treat as 'examples to verify before use' according to the final note?