fix(cursor): use resolved OAuth model for runs#132
Merged
Conversation
This was referenced Jul 10, 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.
Replaces the oauth-model-alias portion of contributor PR #124 (original commit 59b83e0) with a narrow, tested fix.
The conductor already resolves a Cursor OAuth alias into req.Model. Cursor Run construction now sends that resolved upstream model on every initial, auth-migration, and cold-resume path, while preserving the client alias in parsed.Model for OpenAI-compatible responses.
Coverage verifies alias override, empty and whitespace fallback, missing client model, and non-mutation. Full go test, build, formatting, diff check, and review passed locally.
Tool-stream changes from #124 are intentionally excluded: there is no safe reproducer and the contributor identified unresolved index/resume/DONE/timeout defects.