Repository navigation
refactor(core): mechanism-neutral context entry rendering - #34945
Merged
Merged
Conversation
The model sees session context, not how it was attached. Baselines render as the bare tagged block; only chronological updates and removals carry narration, phrased without reference to the API.
This was referenced Jul 19, 2026
jinhuang712
pushed a commit
to jinhuang712/opencode
that referenced
this pull request
Sep 26, 2026
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
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 #34941, from review feedback.
The "An API client attached..." preamble leaked the delivery mechanism into the prompt. The model doesn't need to know how context arrived — it just needs the context, and the
<context key="...">block is already self-describing.The context under "<key>" changed and supersedes the previous value:+ blockThe context under "<key>" no longer applies. Disregard it.No wire or schema changes; phrasing is server-owned. A human-readable
descriptionpayload field remains an add-later-compatible option if a real need appears.