Description

GitHub Copilot authentication in Goose Desktop on Windows gets stuck at the "Signing in..." screen. The browser window does not automatically open, and no authentication code is displayed or copied to the clipboard.

Environment

• OS: Windows 11
• Goose Version: v1.23.0
• Installation Method: Direct download (Goose-win32-x64.zip)
• Goose Type: Desktop Application
• GitHub Copilot: Active subscription confirmed

Steps to Reproduce

1. Launch Goose Desktop on Windows
2. Select "Other Providers" from the welcome screen
3. Click "Configure providers"
4. Select "GitHub Copilot" from the provider list
5. Click "Configure" or "Sign in with GitHub Copilot"
6. Application displays: "Sign in with your GitHub Copilot account to use this provider" with "Signing in..." and "A browser window will open for you to complete the login."

Expected Behavior

• Browser should automatically open to https://github.com/login/device
• An 8-character authentication code should be displayed in the Goose window
• The code should be automatically copied to clipboard
• User can complete authentication in the browser

Actual Behavior

• Browser window does not open automatically
• No authentication code is displayed in the Goose application
• No code is copied to clipboard
• Application remains stuck on "Signing in..." screen indefinitely
• No error messages are shown
• No entries are created in ~/.config/goose/ directory

Attempted Workarounds

• Manually opening https://github.com/login/device in browser (no code to enter)
• Checking clipboard with Ctrl+V (nothing pasted)
• Restarting Goose Desktop application
• Running Goose as Administrator
• Checking Windows Firewall settings
• Checking antivirus exclusions

Additional Context

• The same GitHub Copilot subscription works correctly in VS Code
• Similar issues have been reported for WSL (Goose + Github Copilot in WSL: OAuth authentication failed for GITHUB_COPILOT_TOKEN #6607) but this is native Windows Desktop
• Issue Windows on arm support for Goose desktop #3068 mentions GitHub Copilot asking for token instead of device flow on Windows
• The Goose Desktop process is running (visible in Task Manager)
• No error logs are generated in %USERPROFILE%\.config\goose\

Logs

No log files are created. The ~/.config/goose/ directory remains empty after attempting authentication.

Workaround

Using Google Gemini as an alternative provider works correctly with API key authentication.

Impact

Users on Windows cannot authenticate with GitHub Copilot through the Desktop application, forcing them to:

1. Use alternative providers (Gemini, OpenAI, etc.)
2. Use WSL instead of native Windows
3. Cannot utilize their existing GitHub Copilot subscription with Goose

Suggested Fix

• Ensure the device flow authentication properly triggers on Windows Desktop
• Display the authentication code in the UI if browser fails to open
• Provide manual copy button for the authentication code
• Show error messages if authentication flow fails to start
• Create log files with debugging information

Related Issues

• Goose + Github Copilot in WSL: OAuth authentication failed for GITHUB_COPILOT_TOKEN #6607 (WSL OAuth issue - different from this native Windows issue)
• Windows on arm support for Goose desktop #3068 (Mentions GitHub Copilot token request on Windows)