fix: merge consecutive system messages for OpenAI providers#710
Merged
fix: merge consecutive system messages for OpenAI providers#710
Conversation
OpenAI reasoning models (e.g., gpt-5-nano) don't handle multiple consecutive system/developer messages well, producing empty responses. This adds a provider-specific mergeConsecutiveSystemMessages transform in LLMExecutor, following the existing filterReasoningPartsForProvider pattern. Only applies to openai and azure-openai providers. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.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
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
mergeConsecutiveSystemMessagestransform inLLMExecutorthat joins consecutive system messages into one, following the existingfilterReasoningPartsForProviderpatternopenaiandazure-openaiproviders — Anthropic and others keep separate system blocks for optimal cache controlTest plan
🤖 Generated with Claude Code