Repository navigation
Use native Responses for the DeepSeek Copilot route - #890
Merged
Merged
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
pelikhan
marked this pull request as ready for review
November 21, 2026 23:44
Contributor
|
🧠 Matt Pocock Skills Reviewer is reviewing this pull request using Matt Pocock's engineering skills... |
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.
The DeepSeek integration failed before the judges started: AWF could not translate the outer CLI's Chat Completions request to
/responsesforgpt-5.3-codexwithout droppingstore.Select native Responses in the shared DeepSeek provider configuration so the outer CLI and all three SDK judges use the same AWF-discovered route. Both Harness pins remain
0.2.0-rc.2; gateway controls, the model, and the three-judge assertions are unchanged.Validation: A Responses-only loopback test verified one outer CLI request and exactly three SDK judge requests, all with
store: false. All 738 tests and typecheck passed. No workflow was manually dispatched.