Repository navigation
fix: restore Grok OAuth requests for 0.1.21 - #84
Merged
Merged
Conversation
pavelhov
changed the title
pavelhov
marked this pull request as ready for review
October 21, 2026 16:06
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.
Grok OAuth requests can use the subscription proxy again after xAI began rejecting CodexCommander's advertised client version with HTTP 426. The compatibility profile now advertises 1.0.52, with the User-Agent derived from the same value, and prepares version 0.1.21 for the app updater.
Validation: the outgoing-header regression passes; a live
xai/grok-4.7request through Commander's/v1/responsescompleted with streaming HTTP 200, resolved modelgrok-4.7, and the correct arithmetic answer in 2.2 seconds.bun run typecheck,bun run test:parallel(all 631 files),bun run privacy:scan, docs build, GUI lint/i18n lint, GUI tests (888 passed), and GUI build passed.Security review: independent review found no blocking issues. Credential destinations, OAuth/token handling, API-key isolation, case-insensitive user header overrides, and request-ID behavior are unchanged. No credential or request-body logging, dependency changes, or workflow changes are introduced.
After integration into
development, a separate promotion tomainand an authenticated universal macOS preview release will deliver the fix to installed apps.