It appears that adding user metadata in the latest versions causes Google to end up requesting verification for each account.

[titet11]

Pre-submission checklist

• I have searched existing issues and feature requests for duplicates
• I have read the README

Feature description

1. Just a few minutes ago, all my Google accounts started requiring additional verification to log in.

2. I didn't have this problem with previous versions.

3. I updated this extension to the latest version yesterday.

4. I used the Antigravity app to log in with the same account, and it asked me to verify my account in the same way as the extension.

5. Now all my Google accounts require verification.

6. I'm using Windows 11 22H2.

7. After the problem started, I replaced all the UserAgents with Windows 10 64-bit, but it didn't fix it.

8. I'm using Open Code Desktop 1.1.48.

9. The extension takes 2 minutes to detect the error with a single account.

10. I am using all the default round-robin values, as I have more than 20 active accounts, and I have also enabled the high-performance setting for round-robin, but it still takes 2 minutes to detect the error on a single account.

Use case

I believe that the implemented metadata, far from fixing anything, only caused more problems.

Proposed implementation

No response

Alternatives considered

No response

Compliance

• This feature is for personal development use
• This feature does not violate or circumvent Google's Terms of Service

Additional context

No response

[github-actions]

👋 Thanks for opening this issue!

Thank you for reporting this issue. I can confirm this is a bug/regression related to account verification, not an enhancement.

Root Cause: Recent updates added Client-Metadata headers (containing IDE type, platform, and plugin type) that are sent during OAuth flows. This additional metadata appears to trigger Google's verification requirements for certain account patterns, especially when using multiple accounts with round-robin configuration.

Immediate Workarounds:

1. Wait for PR fix: implement proper VALIDATION_REQUIRED error handling with progressive cooldown #338 - This fix is already in progress and implements proper VALIDATION_REQUIRED error handling with progressive cooldown (10m → 1h → 6h → 24h)
2. Downgrade temporarily - If critical, you can downgrade to v1.2.x which doesn't send the metadata headers
3. Complete verification once - The verification requirement should persist for each account after completing it once

Related Issue: This is essentially the same issue as #335 (403 PERMISSION_DENIED – VALIDATION_REQUIRED), which is being addressed in PR #338.

Why your accounts are affected: With 20+ accounts using round-robin, the metadata changes likely triggered Google's risk detection for multiple accounts accessing the same service with similar patterns. The error detection taking 2 minutes per account is due to the current lack of proper VALIDATION_REQUIRED error handling - this will be fixed in PR #338.

I'll update the labels on this issue to reflect it's a bug in the auth system. The fix should be available in the next release.

🔗 This appears to be related to #335. Please check that issue for updates.

---

This is an automated response. A maintainer will review your issue soon.

[titet11]

I hope you do something about this because this problem is frustrating me.