{"version":"2.1.268","anchor":"new-tracecontext-field-attached-to-remote-relayed-prompt-mes","canonical_anchor":"tracing-headers-for-cross-session-turns-via-a-specific-mcp-c","heading":"Trace context now propagated for remote-relayed turns","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/new-tracecontext-field-attached-to-remote-relayed-prompt-mes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Trace context now propagated for remote-relayed turns\n\nClaude Code now attaches trace context to messages relayed across sessions when running in remote mode\n\n**Unclear.** What traceContext is used for, or what consumes it, is not stated.\n\n**What**\n\nClaude Code now extracts and propagates a `trace_context` (a `traceparent` value) and an event UUID when a turn is merged across sessions. This is sent as `anthropic\/ccr-turn-event-uuid` and `anthropic\/ccr-turn-linked-event-uuids` request headers.\n\nWhen building the internal message for an incoming user message, a new `traceContext` field is now attached to it as well, computed via a new helper.\n\nThis behavior only applies when `CLAUDE_CODE_REMOTE` is set, and part of it is further gated to a specific dynamic-scope MCP server configuration.\n\n**Why**\n\nThis helps trace and correlate related turns and messages when Claude Code is operating in a remote\/cross-session mode, which is useful for debugging and observability but has no direct effect on typical local usage.\n\n- Area: Sessions\n- Names: `CLAUDE_CODE_REMOTE`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}