diff --git a/docs/platforms/javascript/common/agent-tracing/index.mdx b/docs/platforms/javascript/common/agent-tracing/index.mdx index c9e317fe0242c..536a7728febd6 100644 --- a/docs/platforms/javascript/common/agent-tracing/index.mdx +++ b/docs/platforms/javascript/common/agent-tracing/index.mdx @@ -83,20 +83,14 @@ Pick your AI stack. Some libraries auto-instrument; others need a short setup -On Cloudflare, setup differs by library—open the guide for your stack: - -- **Workers AI** — works automatically once Sentry wraps your worker. -- **Vercel AI** — turn the integration on in your Sentry options, then enable telemetry on each AI call (details on that page). -- **OpenAI, Anthropic, Google GenAI, LangChain, LangGraph** — not auto-instrumented here. Each guide shows how to wrap your client so AI spans show up. Tracing alone is not enough. - -- Workers AI -- Agents SDK -- Vercel AI -- OpenAI -- Anthropic -- Google Gen AI -- LangChain -- LangGraph +On Cloudflare, how much setup you need depends on the library. Enabling tracing alone is not enough for most of them. + +- Workers AI — works as soon as Sentry wraps your worker. Nothing else to do. +- Vercel AI — add the integration to your Sentry options, then enable telemetry on each AI call. +- Agents SDK — wrap your agent classes with `instrumentAgentWithSentry`. +- OpenAI, Anthropic, and Google Gen AI — wrap your client instance. +- LangChain — attach Sentry's callback handler. +- LangGraph — wrap your graph before you call `.compile()`.