[FEATURE]: propagate incoming trace context for HTTP requests

[Betula-L]

• I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

When OpenCode receives an HTTP request with traceparent / tracestate, it should extract that context and carry it through request handling.

Today those headers stop at the server boundary, so request traces start disconnected instead of attaching to the upstream trace.

This is a small core piece of the broader tracing work:

• Add OTEL export capabilities for observability and monitoring #12142 covers broader OTEL export / observability support
• Feature Request: Add Langfuse Tracing #219 covers Langfuse-related usage

[github-actions]

This issue doesn't fully meet our contributing guidelines.

What needs to be fixed:

• No issue template was used. This appears to be a feature request but the title does not start with [FEATURE]:, and the required feature request template fields (verification checkbox, structured description) are missing. Please use one of the three supported templates: Bug Report, Feature Request, or Question.
• Feature requests should explain the problem or user need more concretely, and include the verification checkbox confirming no duplicate exists.

Please edit this issue to address the above within 2 hours, or it will be automatically closed.

---

This issue might be a duplicate of existing issues. Please check:

• Add OTEL export capabilities for observability and monitoring #12142: Add OTEL export capabilities for observability and monitoring (same OTEL/telemetry scope)
• Feature: Add sessionID to experimental.chat.system.transform hook for tracing integration #6142: Feature: Add sessionID to experimental.chat.system.transform hook for tracing integration (OTEL tracing integration)
• [FEATURE]: Forward session & parent-session IDs as HTTP headers in LLM API requests #12930: [FEATURE]: Forward session & parent-session IDs as HTTP headers in LLM API requests (related HTTP header propagation)

If you believe this was flagged incorrectly, please let a maintainer know.

[github-actions]

Thanks for updating the issue! It now follows the contributing guidelines and looks good. We appreciate you taking the time to revise it.

[ChristianKniep]

Any progress on that one? Really like the idea to get a comprehensive

[github-actions]

To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.