Cloudflare Adds Agent Tracing, with Truncation Limits and Uneven Payload Defaults
Cloudflare's agent tracing is now GA—but watch the October billing shift: every span becomes a billable event.
Why it matters
Cloudflare expanded Workers observability to cover agent workflows (invocations, model calls, tool runs, approvals), enabling turn-by-turn session replay. Practitioners deploying agents on Cloudflare need to understand payload truncation defaults vary by framework, and plan for billing changes starting October 1, 2026.
The key facts
11 to knowAgent tracing added to Cloudflare Workers: agent invocations, model calls, tool runs, approvals tracked as spans
Session replay supports turn-by-turn debugging
Traces are not lossless; payloads may be truncated
Payload recording defaults differ by framework
Billing change effective October 1, 2026: every span becomes billable
Source: InfoQ / Steef-Jan Wiggers
Agent tracing spans invocations, model calls, tool runs, and approvals within Workers traces
Session replay available turn-by-turn; traces are not lossless, payloads may be truncated
Payload recording defaults vary by framework
Billing change effective October 1, 2026: every span becomes a billable event
Published August 15, 2026
Go to the source
InfoQ AI/MLinfoq.com
Publisher excerpt: Cloudflare launched agent tracing, adding spans for agent invocations, model calls, tool runs, and approvals to existing Workers traces. Sessions replay turn by turn, though the docs warn traces are not lossless and payloads may be truncated. Payload recording defaults differ by framework, and from…