---
id: agent-opentelemetry-baggage-and-context-propagation
title: 'Agent OpenTelemetry Baggage and Context Propagation'
schema_type: TechArticle
category: ai
language: en
confidence: medium
last_verified: '2026-06-03'
created_date: '2026-06-03'
generation_method: ai_structured
derived_from_human_seed: true
conflict_of_interest: none_declared
is_live_document: false
data_period: static
atomic_facts:
  - id: fact-ai-agent-opentelemetry-baggage-and-context-propagation-1
    statement: >-
      OpenTelemetry documentation describes Baggage as contextual information
      that resides next to context.
    source_title: OpenTelemetry Baggage
    source_url: https://opentelemetry.io/docs/concepts/signals/baggage/
    confidence: medium
  - id: fact-ai-agent-opentelemetry-baggage-and-context-propagation-2
    statement: >-
      OpenTelemetry documentation says Baggage can pass data across services and
      processes, making it available to add to traces, metrics, or logs.
    source_title: OpenTelemetry Baggage
    source_url: https://opentelemetry.io/docs/concepts/signals/baggage/
    confidence: medium
  - id: fact-ai-agent-opentelemetry-baggage-and-context-propagation-3
    statement: >-
      The W3C Baggage specification says the baggage header is used to propagate
      user-supplied key-value pairs through a distributed request.
    source_title: W3C Baggage
    source_url: https://www.w3.org/TR/baggage/
    confidence: medium
completeness: 0.82
known_gaps:
  - Baggage safety depends on propagation boundaries, automatic instrumentation behavior, header size limits, sampling, vendor processors, and whether sensitive fields are filtered before third-party requests.
disputed_statements: []
primary_sources:
  - title: OpenTelemetry Baggage
    type: documentation
    year: 2026
    url: https://opentelemetry.io/docs/concepts/signals/baggage/
    institution: OpenTelemetry
  - title: W3C Baggage
    type: standard
    year: 2021
    url: https://www.w3.org/TR/baggage/
    institution: World Wide Web Consortium
secondary_sources: []
updated: '2026-06-03'
ai_models:
  - gpt-5-codex
---

## TL;DR

OpenTelemetry Baggage gives agents a source-mapped way to reason about request-scoped context that travels across service boundaries.

## Core Explanation

Agent runs often cross services, queues, tools, and worker processes. Trace IDs show where a request went, but baggage can carry small contextual key-value pairs that help correlate telemetry with tenant, workflow, experiment, or task identifiers.

That power needs restraint. Baggage is propagated with context and can leave the original service boundary through HTTP headers. Agents should inspect which keys are set, which propagators are enabled, whether automatic instrumentation forwards them, and whether any key can reveal user, tenant, or secret-adjacent information.

## Source-Mapped Facts

- OpenTelemetry documentation describes Baggage as contextual information that resides next to context. ([source](https://opentelemetry.io/docs/concepts/signals/baggage/))
- OpenTelemetry documentation says Baggage can pass data across services and processes, making it available to add to traces, metrics, or logs. ([source](https://opentelemetry.io/docs/concepts/signals/baggage/))
- The W3C Baggage specification says the baggage header is used to propagate user-supplied key-value pairs through a distributed request. ([source](https://www.w3.org/TR/baggage/))

## Further Reading

- [OpenTelemetry Baggage](https://opentelemetry.io/docs/concepts/signals/baggage/)
- [W3C Baggage](https://www.w3.org/TR/baggage/)