OBSERVABILITY Signal 450
Cloudflare adds agent tracing to Workers with framework-dependent payload defaults and truncation limits
↗
Cloudflare launched agent tracing for Workers, adding spans for agent invocations, model calls, tool runs, and approvals, though the feature carries truncation limits and inconsistent payload storage defaults across frameworks.
Teams debugging agents that return HTTP 200 but fail internally can now see model calls, tool arguments, and subagent nesting in a single trace waterfall. However, payload defaults vary by framework, Think and wrapAISDK() store nothing by default while Flue stores everything, meaning privacy and debugging coverage depend on which harness a team chose.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
Agent tracing adds spans for invocations, model calls, tool execution, and approvals to existing Workers traces, nesting subagent work under the parent operation.
Payload recording defaults differ across frameworks: Think and wrapAISDK() require explicit opt-in to store messages and tool payloads, while Flue stores them by default.
Traces are not lossless, long payloads may be truncated, session replay does not display images, and approval spans do not measure human response latency across invocations.
THE CLUSTER