
Cloudflare has added a way for developers to watch what an AI agent does step by step: which model it called, which tools it ran, where a human approved something. It sits inside the tracing tools Cloudflare already offered on its Workers platform.
For most businesses in the North Phoenix area, this changes nothing today. If your site is a set of pages, a contact form and maybe a booking tool, you almost certainly do not have an AI agent running on Cloudflare, and none of this applies. It gets attention because a lot of small software is now being built with AI agents in the middle of it, and until recently nobody could see what those agents were actually doing when they went wrong.
Two details are worth holding on to, though, if you do have a chatbot or an automated assistant that someone built for you.
The first is money. From 1 October 2026, every one of these recorded steps counts as a billable event. A single customer conversation can produce a lot of steps. If a developer switches tracing on now while building, and nobody switches it off or scales it back, you could be looking at a bill that behaves quite differently after that date than it does today. That is not a reason to panic. It is a reason to know whether it is on.
The second is what gets recorded. Cloudflare says the recording is not complete, and that longer content may be cut short. It also says the default for recording the actual content of a conversation varies depending on which framework the developer used. That means whether your customers' typed messages are being stored somewhere may currently be an accident of a tool choice rather than a decision anyone made. If you take health information, financial details, or anything else you would not want sitting in a log, that matters.
What to do: if you have no AI agent, nothing. If you do, ask whoever built it two questions: is tracing turned on, and is it recording the content of what customers type. Then put a note in your calendar for mid 2026 to check the billing side before the October date.
Reported by:

