What is ChatGPT-Operator?
ChatGPT-Operator identifies web access made while OpenAI's agent carries out a task requested by a ChatGPT user. The agent works through a browser and can inspect pages, click controls, type into supported fields, and scroll. It is closer to delegated browsing than to a crawler building an index.
OpenAI introduced Operator as a separate research-preview product, then integrated its capabilities into ChatGPT agent mode in 2025. The standalone Operator site was retired. The ChatGPT-Operator name can still matter in bot catalogs, logs, and platform rules even though users now start the workflow inside ChatGPT.
Requests are tied to a user's task and can arrive in a short sequence as the browser moves through a site. A page view does not prove the agent completed the task, because a login requirement, confirmation step, CAPTCHA, or site policy may stop the workflow. The user can also take over when human input is required.
This traffic does not control inclusion in ChatGPT search. ChatGPT-Operator is not an automatic web-indexing crawler, and allowing it will not make a page rank or appear as a search citation. OAI-SearchBot is the separate identity for ChatGPT search discovery.
The bot record also states that ChatGPT-Operator is not used for AI training. GPTBot is OpenAI's separate training crawler. A site can therefore make different decisions for agent access, search inclusion, and potential training instead of treating every OpenAI request as the same use.
The stored token is ChatGPT-Operator. For current ChatGPT cloud-browser traffic, OpenAI also documents Web Bot Auth signatures: the Signature-Agent value is "https://chatgpt.com", and public keys are available at https://chatgpt.com/.well-known/http-message-signatures-directory. Signature verification is stronger evidence of origin than a user-agent string on its own.
