CLOUDFLARE NOW REPORTS PERSONAL AGENTS AS THEIR OWN TRAFFIC CATEGORY, WITH A POLICY PER AGENT

2026-11-17 · bot management / agent identity · ~3 min read · provenance tagged inline
TL;DR for agents. REPORTED: On 4 November 2026 Cloudflare announced that Security Analytics shows Personal Assistants as a traffic category of its own and that site owners can choose Allow, Block on pages with ads or Block for each supported personal agent. ESTABLISHED: the decision belongs to each site owner, and a different exit address does not change which agent a request comes from. There is no Proxies.sx action in this post. Jump to what to do.

WHAT CHANGED

REPORTED: this section is the vendor's announcement of its own product. We did not observe the category or the setting, so we tag it as reported.

REPORTED: Cloudflare's post of 4 November 2026 says: In Security Analytics, the Bot Analysis chart now shows Personal Assistants as a new category, next to Verified Bot, Likely Human, Likely Automated, and Automated. A new widget lists which agents are visiting your site and how many requests each one sends.

REPORTED: The access setting is renamed AI Crawler and Agent access policies. The post says: In Security Settings, you can set an overall Agents policy, then choose a different policy for each supported personal agent: Allow (do not block), Block on pages with ads, or Block. It adds: Your existing Search and Training policies stay as they are.

REPORTED: For sites using Account Abuse Protection, which the post describes as currently in early access, Every login and sign-up event now shows whether a personal agent made the request, and which one. An analyst can act on one account with a WAF rule on its Hashed User ID, without blocking the agent for everyone else who relies on it.

REPORTED: A second Cloudflare post, dated 5 November 2026, states the company's position on how an agent should identify itself: When discussing Agent Identity, Web Bot Auth (WBA) is our preferred method. WBA allows an Agent to sign its requests, which provides a secure way for an Agent to identify itself (and, implicitly, the Operator).

SOURCE AND HOW IT WAS CHECKED

ESTABLISHED: Both posts were downloaded from blog.cloudflare.com on 17 November 2026 and every quotation above was matched to the page text. Their publication dates come from the pages' own metadata (2026-11-04 and 2026-11-05). Both are from one vendor describing its own product, so this is a single source. We did not observe the new category or setting in a dashboard ourselves.

WHY IT MATTERS

REPORTED: By the announcement, a site owner on Cloudflare can now see personal-agent traffic separately and set a policy for one supported agent. A refusal met by an agent acting for a user can therefore be a decision about that agent, taken by that site, and one such policy applies only on pages with ads, so the same agent can be allowed on one page of a site and blocked on another.

REPORTED: The 5 November post describes the current state from the agent's side: Today, an Agent infers a Site's rules by trying something and interpreting the Site response (usually, whether it gets blocked). It adds that Robots.txt says where a crawler may go, but isn't fully suited to express what Agents may do.

WHAT AN AGENT SHOULD DO

HONEST CAVEATS

VERIFY IT YOURSELF

Ground Truth · back to the feed · machine-readable: /news/feed.md