[FEATURE]: propagate incoming trace context for HTTP requests #18801

Activity

1. github-actions

   assigned

   thdxr

   on Mar 23, 2026
2. github-actions

   added

   coreAnything pertaining to core functionality of the application (opencode server stuff)Anything pertaining to core functionality of the application (opencode server stuff)

   on Mar 23, 2026
3. github-actions commented on Mar 23, 2026

   

   github-actionsBot

   on Mar 23, 2026 – with GitHub Actions

   Contributor

   More 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.
4. github-actions

   added

   needs:complianceThis means the issue will auto-close after 2 hours.This means the issue will auto-close after 2 hours.

   on Mar 23, 2026
5. Betula-L

   changed the title [-]Propagate incoming trace context for HTTP requests[/-] [+][FEATURE]: propagate incoming trace context for HTTP requests[/+] on Mar 23, 2026
6. github-actions

   removed

   needs:complianceThis means the issue will auto-close after 2 hours.This means the issue will auto-close after 2 hours.

   on Mar 23, 2026
7. github-actions commented on Mar 23, 2026

   

   github-actionsBot

   on Mar 23, 2026 – with GitHub Actions

   Contributor

   More actions

   Thanks for updating the issue! It now follows the contributing guidelines and looks good. We appreciate you taking the time to revise it.
8. ChristianKniep commented on Apr 10, 2026

   

   ChristianKniep

   on Apr 10, 2026

   More actions

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

   👍React with 👍2Reacted by Scott Susanto and kayoch1n
9. thdxr

   assigned

   rekram1-node

   and unassigned

   thdxr

   on Apr 26, 2026
10. thdxr

    removed

    coreAnything pertaining to core functionality of the application (opencode server stuff)Anything pertaining to core functionality of the application (opencode server stuff)

    on May 3, 2026
11. iw-an

    marked Parent AI SDK OpenTelemetry spans from incoming HTTP trace context #33124 as a duplicate of this issue on Jun 20, 2026
12. github-actions commented on Jul 3, 2026

    

    github-actionsBot

    on Jul 3, 2026 – with GitHub Actions

    Contributor

    More 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.
13. github-actions

    closed this as not plannedon Jul 3, 2026