From ed20c05b9ae499b9a9962d3eb3d3d38ae0bc01d8 Mon Sep 17 00:00:00 2001
From: Charly Gomez <charly.gomez1310@gmail.com>
Date: Thu, 17 Sep 2026 18:30:34 +0200
Subject: [PATCH] docs(nextjs): Note Vercel AI is not instrumented on the Edge
 runtime

The Vercel AI instrumentation relies on diagnostics channels, which the
Edge runtime doesn't support. @sentry/nextjs keeps the vercelAIIntegration
export on its Edge build as a no-op, so it captures no spans there.

Refs SDK-1483
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
---
 .../common/configuration/integrations/vercelai.mdx     | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/docs/platforms/javascript/common/configuration/integrations/vercelai.mdx b/docs/platforms/javascript/common/configuration/integrations/vercelai.mdx
index 0fde1e1a9fcb2..46395ea603f29 100644
--- a/docs/platforms/javascript/common/configuration/integrations/vercelai.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/vercelai.mdx
@@ -29,6 +29,16 @@ Sentry.init({
 });
 ```
 
+<PlatformSection supported={['javascript.nextjs']}>
+
+<Alert level="warning">
+
+The Edge runtime isn't instrumented. The instrumentation relies on diagnostics channels, which Edge doesn't support. `@sentry/nextjs` still exports `vercelAIIntegration` from its Edge build so imports resolve, but it captures no spans. Run AI calls in the Node runtime.
+
+</Alert>
+
+</PlatformSection>
+
 <Alert level="warning">
 
 Don't use the AI SDK's `registerTelemetry` API (AI SDK v7 and above) together with this integration. `vercelAIIntegration` already instruments the AI SDK, so registering telemetry separately produces duplicate spans.