What is Anchor Browser?
Anchor Browser is managed browser infrastructure for AI agents. Anchor's documentation describes cloud sessions that can navigate websites, authenticate, fill forms, and extract information. Developers can run a natural-language task or connect automation through browser tooling and Anchor's APIs.
A visit therefore belongs to an interactive browser workflow, not a bulk indexing crawl. One task may load several pages, maintain session state, and submit forms in the same way a remote browser would. Whether a human initiated the task directly or an application launched it depends on the Anchor integration using the session.
Sites should evaluate this traffic like delegated automation. Existing login checks, account permissions, and transaction safeguards still apply. Allowing Anchor Browser through a bot filter does not grant the agent authority to act for a particular user.
Anchor does not document this browser as a model-training collector or a public search indexer. Blocking it will not opt a site out of AI training, and allowing it does not improve general AI search placement. The direct consequence is whether Anchor-backed agents can complete browser tasks on the site.
Cloudflare's bot directory records the user agent as exactly Anchor Browser and says it does not follow robots.txt. The bot metadata leaves robots behavior unknown. A robots rule is still useful as a policy notice, but application and edge controls are needed for enforcement.
Anchor Browser supports Web Bot Auth. Cloudflare's bot directory lists its signature directory at https://api.anchorbrowser.io/.well-known/http-message-signatures-directory. A valid HTTP Message Signature confirms that a request came through the registered Anchor infrastructure; it does not identify the end user or prove that the requested action is authorized.
