fix: register OTel context manager so AI SDK spans thread into Effect traces#22645
Merged
Conversation
… traces @effect/opentelemetry creates a NodeTracerProvider but never calls register(), leaving the global @opentelemetry/api context manager as the no-op default. The AI SDK calls tracer.startActiveSpan() which relies on context.active() to find parent spans — without a real context manager every AI SDK span started a new trace. Registering AsyncLocalStorageContextManager before the NodeSdk layer fixes this. Verified with motel: traces went from singleton AI SDK spans to 400+ spans properly threaded under SessionPrompt.prompt.
xywsxp
pushed a commit
to xywsxp/opencode
that referenced
this pull request
Apr 24, 2026
dgokeeffe
pushed a commit
to dgokeeffe/opencode-databricks
that referenced
this pull request
May 6, 2026
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
1 participant
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.
Summary
AsyncLocalStorageContextManageron the global@opentelemetry/apicontext before the@effect/opentelemetryNodeSdk layer is created@opentelemetry/apiand@opentelemetry/context-async-hooksas direct dependencies (both were already transitive)Problem
Every AI SDK span (
ai.streamText,ai.streamText.doStream,ai.toolCall) appeared as a singleton trace — no parent-child threading. Effect spans worked fine (300+ spans in a single trace), but AI SDK spans each started a new trace.Root Cause
@effect/opentelemetry'sNodeSdkcreates aNodeTracerProviderbut never callsprovider.register(). Without that call, noAsyncLocalStorageContextManageris set on the global@opentelemetry/apicontext. The AI SDK'stracer.startActiveSpan()callscontext.active()which returnsROOT_CONTEXTevery time → every span starts a new trace.Evidence (via motel)
Before:
ai.streamTexton traceIdf0fa2077...(spanCount: 1),ai.streamText.doStreamon traceId30ddcf61...(spanCount: 1) — even the AI SDK's own parent/child is broken.After:
SessionPrompt.prompttrace has 400 spans — Effect + AI SDK all threaded together under a single traceId.