Cloudflare launches the Trusted Agent Delegation coalition and lets sites see which personal agent made a login, then block one account without blocking the agent
Cloudflare argues that sites lose sight of the user behind an agent and bear the cost when things go wrong, and ships first tools to tie agent traffic back to users.
// Key points
- The post lists problems agents reintroduce for sites, including shared subscriptions, friendly fraud on agent purchases, credential stuffing through a shared agent, and content read without a visit
- The Trusted Agent Delegation (TAD) coalition will examine existing protocols such as Web Bot Auth, OAuth and MOLE and bring well-defined problems to the IETF
- Security Analytics now breaks out Personal Assistants as a traffic category, and AI Crawler and Agent access policies can allow or block each agent, including only on pages with ads
- With Account Abuse Protection (early access), each login and sign-up shows whether a personal agent made it and which one, so a site can mitigate one account by its Hashed User ID
Builder's takeWith yesterday's 402 payouts, the sites side now has both a price and an identity layer for agents. If your product has a login page, start logging which logins come through agents now; once the data shows up, decide which flows need a real person and which can let agents through.
// Background · from #AI agents
Full timeline →- Nov 7 AWS runs Claude Code as a remote agent on Bedrock AgentCore: one microVM per task, up to three attempts, and a draft pull request unless verification passes
- Nov 7 Anthropic on agent memory: "dreaming" over 128 sessions lifts a wiki-only score from 13% to 48%, and wiki plus search saves about 20,000 tokens per question
- Nov 7 Mistral Studio adds managed agents and apps, with skills, sandboxes, subagents, hooks and OpenTelemetry traces, deployable in your own VPC or on-premises