first issue

[SenseAli]

Is your feature request related to a problem?

I believe the issue is that the baggage.set_baggage(key, value) does not read the current context that later gets called by get_all( ). instead it creates a new Context object with the baggage entry added and returns but the newer context is never made "current"

Describe the solution you'd like

i guess use attach( ) with each context to make it current and then use detach( ) when it is complete

from opentelemetry import baggage, context, trace

tracer = trace.get_tracer(name)

global_ctx = baggage.set_baggage("context", "global")
token_global = context.attach(global_ctx)

with tracer.start_as_current_span(name="root span") as root_span:
parent_ctx = baggage.set_baggage("context", "parent")
token_parent = context.attach(parent_ctx)

with tracer.start_as_current_span(name="child span") as child_span:
    child_ctx = baggage.set_baggage("context", "child")
    token_child = context.attach(child_ctx)

Describe alternatives you've considered

No response

Additional Context

No response

Would you like to implement a fix?

Yes

Tip

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.}

[boopathi-376]

I tested this locally with the current source (no code changes made). Here's what I found:

Before — calling set_baggage() without attaching:

from opentelemetry import baggage, context

ctx = baggage.set_baggage("customer_id", "123")

print(baggage.get_baggage("customer_id"))
print(baggage.get_baggage("customer_id", context=ctx))

Output:

None
123

The value is present in the returned Context, but it's not available through the current context.

After — attaching the returned context first:

token = context.attach(ctx)
try:
    print(baggage.get_baggage("customer_id"))
    print(dict(baggage.get_all()))
finally:
    context.detach(token)

print("After detach:")
print(dict(baggage.get_all()))

Output:

123
{'customer_id': '123'}
After detach:
{}

So set_baggage() does create and return a new Context containing the baggage value — it just doesn't make that context current.

Looking at the implementation, set_baggage() follows the same pattern as get_all(), get_baggage(), remove_baggage(), and clear() — they take an optional context and return a value or a new Context, without calling attach() internally. This appears consistent with the current Context API design, where attach()/detach() are separate, explicit operations for changing the current context.

Given that, would it make sense to clarify this behavior in the documentation/examples rather than changing set_baggage()'s behavior? Happy to help with that once there's agreement on the direction.

[wasup-yash]

If this feature is relevant to the repo and roadmap, I would like to work on it, pls clarify?