fix(opencode): serialize orphaned compaction history - #40800
Merged
Conversation
HQ123-BOOP
pushed a commit
to HQ123-BOOP/LibreCode
that referenced
this pull request
Aug 7, 2026
Co-authored-by: Aiden Cline <63023139+rekram1-node@users.noreply.github.com>
6 tasks
charlesverge
pushed a commit
to charlesverge/opencode
that referenced
this pull request
Aug 11, 2026
Co-authored-by: Aiden Cline <63023139+rekram1-node@users.noreply.github.com>
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.
Summary
Why
A split retained tail can begin with an assistant function call. On repeated compaction, the previous compaction scaffold is removed, leaving that function call first in the summarization request. Gemini rejects this ordering because the function call has no preceding user or function-response turn.
Compaction now follows the current V2 approach: history is rendered as textual records such as
[User],[Assistant tool call], and[Tool result], then sent as a single user summarization request. This avoids provider-specific conversation-order constraints without serializing the complete message objects as JSON.Test plan
bun test test/session/compaction.test.ts(53 passed, 1 skipped)bun x prettier --check src/session/compaction.ts test/session/compaction.test.tsRequested by: @rekram1-node (Aiden Cline via Slack)