What is ChatGPT agent?
ChatGPT agent is OpenAI's task-performing agent with its own virtual browser. It visits a site because a ChatGPT user assigned a task, such as finding information or completing steps on the web. This is delegated browser activity, not a background crawl.
According to the OpenAI help page, the agent uses screenshots of its browser window to understand pages. It can navigate, click buttons, and fill forms as the task proceeds. A single run can create a sequence of reads and actions that resembles an interactive browser session.
When a login is needed, the agent can pause and ask the user to take over the virtual browser. OpenAI says screenshots are not captured while the user is controlling it, which lets the user enter a password or other sensitive value. Control can then return to the agent so it can try to continue the workflow.
OpenAI also documents confirmations for high-impact actions, prompt-injection monitoring, and supervised watch mode on some sites. Those product safeguards do not replace a website's own authorization or transaction checks. A site should still decide what the signed-in user may read, change, submit, or purchase.
ChatGPT agent is not the OpenAI crawler used to build search results, and its record gives it no model-training role. OAI-SearchBot and GPTBot are separate identities for those functions. Blocking this agent can stop delegated tasks on the site, but it does not by itself remove the site from ChatGPT search or opt content out of training.
Cloudflare's bot directory lists no stable user-agent pattern for ChatGPT agent. It identifies the agent through Web Bot Auth and gives https://chatgpt.com/.well-known/http-message-signatures-directory as the public key directory. Signature validation is the available way to distinguish covered OpenAI agent requests from a client that merely claims an OpenAI name.
Robots.txt behavior is unknown in this bot, while Cloudflare's bot directory marks followsRobotsTxt as false. Without a stable token, a ChatGPT agent robots.txt block would be guesswork. Sites that want to permit or deny this agent should use signed identity at the edge and ordinary application controls inside authenticated sessions.
