Repository navigation
fix(core): share child session affinity headers - #51923
Merged
Merged
Conversation
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Follow-up to #50495, which made child sessions use the parent's ID for
prompt_cache_keybut left the session headers on the child's own ID. Routers that use the headers, not the body key, still sent sibling subagents to different machines.x-session-affinity,X-Session-Id, andx-opencode-sessionnow use the same affinity value aspromptCacheKey: the parent ID, then the fork root, then the session's own ID.x-parent-session-idstill carries the parent ID.Zen reads
x-opencode-sessionfor sticky provider routing and for per-session usage, so subagent usage now counts toward the parent session there.Verified with the core session runner, compaction, title, and generate tests, plus
bun typecheckinpackages/core.