Repository navigation
[pull] main from danny-avila:main - #179
Merged
Merged
Conversation
* feat: add detached subagent task control * fix: harden detached subagent lifecycle
* ✨ feat: Support Custom Headers On Langfuse Exports Self-hosted Langfuse instances behind an authenticating proxy or API gateway need extra headers on every export request. `@langfuse/otel` already accepts `additionalHeaders` (applied to both the OTLP trace exporter and the media-upload API client), but there was no way to reach it from a run or agent config. Adds `additionalHeaders` to `LangfuseConfig`, passes it through every credential branch of `getLangfuseSpanProcessorParams`, and merges it in `resolveLangfuseConfig` like the other map-valued fields (agent wins). Headers join the destination key. A gateway may route on them, so two otherwise-identical configs can be different projects: excluding them would let a span inherit a parent bound to another destination, and would let a rotated proxy credential keep exporting through the stale cached processor. The digest is order- and case-insensitive so equivalent header maps share one exporter, and hashed because these values are credentials. * 🐛 fix: Merge Langfuse Header Overrides Case-Insensitively Codex review (P1). A plain spread kept both `X-Proxy-Token` and `x-proxy-token` when run and agent configs differed only in casing. HTTP header names are case-insensitive, and filling a fetch `Headers` from that record appends rather than replaces — the exporter would send one comma-joined `run-token, agent-token` value, so the documented agent override never cleanly won and a gateway would see a malformed credential. Merges case-insensitively, keeping the override's casing, matching the case-insensitive identity the destination key already uses.
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )