Skip to content

docs: Fix stale AI integration paths and patterns in AGENTS.md and add-ai-integration skill - #24257

Open
RulaKhaled wants to merge 3 commits into
developfrom
docs/fix-stale-ai-integration-paths
Open

docs: Fix stale AI integration paths and patterns in AGENTS.md and add-ai-integration skill#24257
RulaKhaled wants to merge 3 commits into
developfrom
docs/fix-stale-ai-integration-paths

Conversation

@RulaKhaled

@RulaKhaled RulaKhaled commented Sep 9, 2026

Copy link
Copy Markdown
Collaborator

AGENTS.md and the add-ai-integration skill still describe the pre-server-utils layout, so anyone following them starts in the wrong directory. AI instrumentation now lives in packages/server-utils/src/ai/{provider}/, with the integration in packages/server-utils/src/integrations/{provider}.ts registered via getTracingIntegrations(); runtime packages re-export from @sentry/server-utils.

The patterns were wrong too, not just the paths. vercelAIIntegration consumes no OTel spans: ai >= 7 goes through the SDK's native ai:telemetry tracing channel and v4-v6 through orchestrion-injected channels, so the decision tree is re-rooted on whether an SDK publishes its own diagnostics_channel telemetry. Span ops, streaming, and the shared-utility list were corrected against the source as well.

On truncation: there is none, by design. enableTruncation and all AI truncation/media-stripping logic were removed in #23045, and nothing downstream caps span attributes (maxValueLength covers only request.url and exception values; normalization limits depth/breadth, not string length). The skill now says so explicitly rather than implying contributors must truncate.

Root cause: the docs were not updated when instrumentation was consolidated into server-utils, nor when provider patching moved off OpenTelemetry instrumentation packages onto orchestrion + diagnostics_channel.

🤖 Generated with Claude Code

RulaKhaled and others added 2 commits September 9, 2026 17:11
…ion skill

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
…s_channel

The Vercel AI integration no longer consumes OTel spans: `ai` >= 7 is handled by
subscribing to the SDK's native `ai:telemetry` tracing channel, and v4-v6 by
orchestrion-injected channels. No span processor or event processor remains.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@RulaKhaled RulaKhaled changed the title docs: Fix stale AI integration paths in AGENTS.md and add-ai-integration skill docs: Fix stale AI integration paths and patterns in AGENTS.md and add-ai-integration skill Sep 9, 2026
Resolves the open truncation question and sweeps the sections of the
add-ai-integration skill that were not verified against the tree.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@RulaKhaled
RulaKhaled marked this pull request as ready for review September 9, 2026 15:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant