docs(js): Restructure Vercel AI integration docs - #18925
Merged
Merged
Conversation
Organize setup by platform, share telemetry guidance once, and cut duplicated Cloudflare/non-Cloudflare snippets so readers get one path per runtime without repeated copy.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
vgrozdanic
marked this pull request as ready for review
August 3, 2026 20:04
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
generateObject was dropped during the page restructure. Users on Cloudflare, Deno, and Next.js Edge still need experimental_telemetry on object generation calls for spans to be created. Co-Authored-By: x-ai/grok-4.5 <noreply@opencode.ai>
Separate Node and Edge Sentry.init examples so Next.js users know where to set vercelAIIntegration recordInputs/recordOutputs. Co-Authored-By: x-ai/grok-4.5 <noreply@opencode.ai>
Clarify that force is Node-only; Cloudflare and Deno run the integration when added to integrations without module detection. Co-Authored-By: x-ai/grok-4.5 <noreply@opencode.ai>
Option snippets were standalone factory calls; wrap them so copy-paste registers the configured integration. Co-Authored-By: x-ai/grok-4.5 <noreply@opencode.ai>
Explain re-adding the default integration to configure options, and show Cloudflare option setup with withSentry instead of Sentry.init. Co-Authored-By: opencode <noreply@opencode.ai>
Tell users on auto-enabled platforms how to re-add the integration when they need options. Co-Authored-By: opencode <noreply@opencode.ai>
Hide integration-level recordInputs/recordOutputs examples from Deno and document per-call experimental_telemetry instead. Co-Authored-By: opencode <noreply@opencode.ai>
shellmayr
reviewed
Aug 5, 2026
shellmayr
reviewed
Aug 5, 2026
shellmayr
reviewed
Aug 5, 2026
The page interleaved runtime caveats through every section, so no reader ever saw which combination of runtime and option actually works. Restructure around the two implementations Sentry ships: Node patches the ai module through OpenTelemetry, while Edge, Cloudflare Workers, and Deno cannot load it and read the spans the AI SDK emits on its own. A capability table states each difference once, and the task sections no longer branch per platform. Correct three claims while restructuring: - Edge ignores recordInputs and recordOutputs on the integration. Its option type accepts enableTruncation only, so the previous sentry.edge.config example configured options that do nothing, with no error or warning. - Precedence ran the other way. The integration option wins over the per-call value, not the reverse, so recordInputs: false on the integration cannot be re-enabled at a call site. - AI SDK v7 is unsupported on Edge, which is tracing-channel based. Also fold the per-call material into one section covering isEnabled, the recording overrides, and functionId, and list the instrumented functions. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
coolguyzone
reviewed
Aug 5, 2026
coolguyzone
reviewed
Aug 5, 2026
coolguyzone
reviewed
Aug 5, 2026
coolguyzone
reviewed
Aug 5, 2026
coolguyzone
reviewed
Aug 5, 2026
coolguyzone
reviewed
Aug 5, 2026
coolguyzone
reviewed
Aug 5, 2026
coolguyzone
reviewed
Aug 5, 2026
coolguyzone
reviewed
Aug 5, 2026
coolguyzone
approved these changes
Aug 5, 2026
coolguyzone
left a comment
coolguyzone
left a comment
Contributor
There was a problem hiding this comment.
LGTM, added some suggestions to fix some title casing issues.
Co-authored-by: Alex Krawiec <alexanderkrawiec@gmail.com>
Gate enableTruncation example for Cloudflare withSentry, and stop telling Next.js Node users they must pass experimental_telemetry. Co-Authored-By: opencode <noreply@opencode.ai>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
DESCRIBE YOUR PR
The Vercel AI integration page now walks setup → enable telemetry → capture I/O → options, with shared guidance once and platform sections only where behavior actually differs (Cloudflare entrypoints, Deno/Edge telemetry, Next.js Edge init).
Readers should get a single clear path per runtime without near-duplicate Cloudflare vs non-Cloudflare snippets. Alerts for version floors,
dataCollection, andregisterTelemetryare folded into the relevant sections.Part of TET-2704: Audit Vercel AI on Cloudflare Workers
IS YOUR CHANGE URGENT?
PRE-MERGE CHECKLIST