Open
Conversation
- Add Windows-specific path handling for npm global installs - Handle PowerShell script (.ps1) and command (.cmd) file detection - Maintain backward compatibility with existing behavior - Fixes OAuth credential extraction for Windows users
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.
This PR fixes the Gemini CLI OAuth credential extraction issue on Windows systems.
Problem
The
extractGeminiCliCredentials()function was failing to properly extract OAuth credentials from the installed Gemini CLI on Windows because:Solution
Testing
Fixes the Windows compatibility issue for Gemini CLI OAuth authentication.