docs(js/cf): Fix Agent Tracing and Vercel AI Cloudflare setup - #18859
Merged
Conversation
Cloudflare docs were showing Sentry.init and invalid JS for Agent Tracing and Vercel AI. Use withSentry options, plain CF instrumentation guidance, and dataCollection on enable samples so copy-paste and privacy defaults match the SDK. Co-Authored-By: opencode <noreply@opencode.ai>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
vgrozdanic
marked this pull request as ready for review
July 29, 2026 10:33
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1300062c47
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
ArthurKnaus
approved these changes
Jul 29, 2026
…s_compat
Keep dataCollection: {} for Agent Tracing / Conversations, warn that empty
config is permissive beyond genAI, and point the primary CF Vercel AI setup at
the nodejs_compat entrypoint required for AI SDK v7.
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
2 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
Cloudflare readers following Agent Tracing or Vercel AI docs were steered at
Sentry.init(not a public@sentry/cloudflareAPI) and at integration snippets that either wouldn't parse or implied Node-style auto-instrumentation.Agent Tracing on Cloudflare now bootstraps with
withSentry(and points Durable Objects / Agents atinstrumentDurableObjectWithSentry), keepsdataCollection: {}with a short permissive-defaults warning, and uses a plain-language hub blurb so readers pick the right stack page instead of assuming OpenAI-style auto setup. Vercel AI Cloudflare samples registervercelAIIntegrationonwithSentry, keep Deno/initand Node paths separate, includedataCollection: {}on enable samples, and preserve the default entrypoint vsnodejs_compatrecord*distinction plus per-callexperimental_telemetry.IS YOUR CHANGE URGENT?
PRE-MERGE CHECKLIST