[Bug] Invalid response at the Copilot provider

[rafael-vasconcellos]

Before submitting
☑️ I checked Known Issues
☑️ I searched existing issues

Configuration

• Model: gpt-5
• Provider: Copilot
• Interface: API

Environment

• Python version: 3.12.2
• OS: Windows 11

Bug description
Clear steps to reproduce:

1. Exact command/file used:
   g4f api
2. Environment location: BR

ERROR:g4f.api: Invalid response: {'event': 'challenge', 'method': None, 'parameter': None, 'id': '1'}
Traceback (most recent call last):
  File "C:\Python312\Lib\site-packages\g4f\api\__init__.py", line 461, in chat_completions
    return await response
           ^^^^^^^^^^^^^^
  File "C:\Python312\Lib\site-packages\g4f\client\__init__.py", line 319, in async_iter_append_model_and_provider
    async for chunk in response:
  File "C:\Python312\Lib\site-packages\g4f\client\__init__.py", line 185, in async_iter_response
    async for chunk in response:
  File "C:\Python312\Lib\site-packages\g4f\tools\run_tools.py", line 257, in async_iter_run_tools
    async for chunk in response:
  File "C:\Python312\Lib\site-packages\g4f\providers\asyncio.py", line 73, in to_async_iterator
    async for item in iterator:
  File "C:\Python312\Lib\site-packages\g4f\providers\base_provider.py", line 503, in create_async_generator
    async for chunk in response:
  File "C:\Python312\Lib\site-packages\g4f\providers\asyncio.py", line 73, in to_async_iterator
    async for item in iterator:
  File "C:\Python312\Lib\site-packages\g4f\Provider\Copilot.py", line 80, in create_authed
    async for chunk in cls.create(model, messages, **kwargs):
  File "C:\Python312\Lib\site-packages\g4f\Provider\Copilot.py", line 233, in create
    raise RuntimeError(f"Invalid response: {last_msg}")
RuntimeError: Invalid response: {'event': 'challenge', 'method': None, 'parameter': None, 'id': '1'}

is this "challenge" related to some captcha validation? the Copilot provider require auth now? if so, it should be moved to needs_auth.

[github-actions]

Bumping this issue because it has been open for 7 days with no activity. Closing automatically in 7 days unless it becomes active again.

[hlohaus]

Thank you for reporting this issue with the Copilot provider, @rafael-vasconcellos! We've identified the problem—it stemmed from recent changes to Microsoft's Copilot API, which introduced stricter authentication requirements, including the need for an anon-copilot token.

Update and Resolution

Our code has been updated to handle this properly in the latest version of g4f (please ensure you're on v0.6.3.0 or newer). The provider now fetches and uses the required anon-copilot token automatically when possible, falling back to manual input if needed. This should resolve the "Invalid response" errors you're seeing.

How to Get the Token

The anon-copilot token is a temporary authentication cookie from the official Copilot website (https://copilot.microsoft.com/). Here's how to handle it:

Automatic Fetching (Recommended)

If you have the following set up, g4f will automatically retrieve the token via browser automation—no manual steps required:

• Install the nodriver package: Run pip install nodriver in your Python environment (this is a lightweight browser automation library).
• Install Google Chrome: Ensure you have the latest stable version of Chrome installed on your system. g4f uses it under the hood.
• Usage: Simply select the Copilot provider in your g4f setup (e.g., via the web UI, API, or CLI), and it will handle the rest. The automation opens a headless Chrome instance, logs into Copilot briefly to grab the token, and closes it.

This process is secure and doesn't store any persistent login data—it's just for token extraction.

Manual Method (If Automation Isn't Available)

If you can't use the automatic method (e.g., due to missing dependencies or environment restrictions):

1. Open https://copilot.microsoft.com/ in your browser (Chrome recommended) and start a new chat to ensure you're authenticated (you may need a Microsoft account).
2. Open your browser's Developer Tools (F12 or right-click > Inspect).
3. Go to the Application tab (in Chrome) or Storage tab (in Firefox).
4. Under Cookies > https://copilot.microsoft.com, look for the anon-copilot cookie.
5. Copy its Value (it should be a long string, e.g., starting with eyJ...).
6. Pass this token to g4f:
   • Via API/CLI: Use the provider with the token parameter, e.g., chat.completions(provider="copilot", cookies={"anon-copilot": "your_token_here"}).
   • Via Web UI: If using the g4f web interface, add it the COPILOT_API_KEY environment variable.
   • Note: Tokens expire after a short time (usually 1-2 hours), so you'll need to refresh it periodically.

Testing and Troubleshooting

• After updating g4f (pip install -U g4f or download the latest release), test a simple query with the Copilot provider.
• If you still encounter issues:
  • Check the g4f logs for errors (run with --debug flag if using CLI).
  • Ensure no VPN/proxy is interfering with the automation or API calls.
  • Verify Chrome is in your PATH (e.g., chrome --version in terminal).

This change keeps things compliant with Microsoft's terms while maintaining free access. If you're still hitting snags or have logs/screenshots to share, reply here—we'll get it sorted! Thanks for helping us improve g4f. 🚀

[github-actions]

Bumping this issue because it has been open for 7 days with no activity. Closing automatically in 7 days unless it becomes active again.

[github-actions]

Closing due to inactivity.