Cloudflare Adds Personal Agent Analytics and Per-Agent Access Controls

Cloudflare announced on November 4, 2026, that it is launching analytics for personal-agent activity and more granular access policies, giving site owners a way to identify agents acting for people and set different terms for each supported agent.

The products address a classification problem for websites. A customer may ask an agent to compare products, find support articles, or complete a purchase, but all three interactions arrive as automated traffic. Without knowing which agent is visiting and what it is doing, a business cannot easily distinguish useful customer-directed activity from risk; blocking every agent can also mean turning away customers.

Personal-Agent Traffic Becomes Visible

Security Analytics now lists Personal Assistants as a Bot Analysis category alongside Verified Bot, Likely Human, Likely Automated, and Automated. Selecting it isolates personal-agent traffic over time, separating these requests from the broader automated-traffic view.

A Personal Assistants widget in Top Statistics names the agents visiting a site and counts each one’s requests. Filtering for one agent updates the other widgets to show its requested paths, received status codes, and originating networks. The resulting view can show whether an agent is logging in, reading product pages, reaching checkout, or encountering errors on pages it cannot use.

Sites using Account Abuse Protection, currently in early access, receive a further user-level view. Its population overview shows which personal agents are active across users and how many accounts use them. Login and sign-up events identify whether a personal agent made the request and which one, while fraud teams can filter accounts by AI-assistant events or the number of assistants.

An individual account overview adds the agents associated with that account, allowing an analyst to distinguish an agent with weeks of use from one appearing for the first time. If activity suggests account misuse, the analyst can apply a web application firewall rule to that account’s Hashed User ID rather than block the agent for every other user.

The underlying Account Abuse Protection dashboard was introduced on October 2, 2026. The system takes a customer-configured identifier from a login or sign-up flow, such as an email address, username, or phone number, and cryptographically hashes it into a privacy-preserving, per-domain Hashed User ID that anchors the account’s activity history.

Access Policies Can Vary by Agent

Cloudflare is expanding its existing Agents policy with controls for supported personal agents and renaming the setting AI Crawler and Agent access policies. In Security Settings, a site can establish an overall Agents policy and then choose Allow (do not block), Block on pages with ads, or Block for each supported personal agent.

That structure permits exceptions instead of a single decision covering every agent. For example, a site can block agents generally on pages carrying ads while allowing one supported personal agent. Existing Search and Training policies remain unchanged.

The controls extend the AI traffic policies Cloudflare introduced on July 1, 2026, which separated Search, Agent, and Training behaviors. The Agent category covers automation acting, usually in real time, on a person’s behalf, including chat-fetch bots and browser-use agents. The new per-agent choices operate within that category without changing the separate search or training policies.

Cloudflare also asks during new-zone onboarding whether a site monetizes pages with ads and tailors recommended policies to the answer. The controls remain available later in Security Settings, allowing the initial recommendations to be revisited as a site’s preferences change.

Agent Identity Leaves User Context Unresolved

Cloudflare said its next goal is to preserve the context of a site’s relationship with users when personal agents act as intermediaries. Identifying an agent does not establish whether the person behind it is an existing customer, what actions the person authorized, whether a subscription applies, or which protections should apply.

Its proposed next work involves privacy-aware mechanisms for carrying user context through an agent, helping sites assess reputation, and establishing clear accountability when something goes wrong. Cloudflare plans to share more as it works with agent operators and other ecosystem participants on whether sites can grant agents greater access while maintaining relationships with their users.

For site owners, agent access becomes a concrete business choice rather than a blanket response to automation. The scope for broader access remains tied to a harder requirement: preserving customer relationships when an agent sits between the business and the user.