gemini-cli - 💡(How to fix) Fix Auth Broken for gemini-cli

Bug Report: gemini-cli OAuth Routing and Quota Sync Failure Priority: CRITICAL / P0 Component: @google/gemini-cli Authentication / Billing Sync Reported By: [email protected] Environment OS: Fedora Asahi Linux Shell: Zsh Account Status: Active Google AI Plus Subscriber CLI Versions Tested: @google/gemini-cli@latest (v0.41.2) and v0.41.1 Issue Description The gemini-cli is failing to correctly sync the Google AI Plus subscription status during the OAuth flow. After successfully authenticating via browser OAuth (bypassing the FIDO/Titan key udev hardware loop), the CLI incorrectly reports Pro usage is at 100% capacity (0/0 allowed), immediately locking out the user despite no recent usage. Steps to Reproduce Clear all CLI configuration files (rm -rf ~/.config/configstore/gemini* ~/.config/@google* ~/.genai*). Execute gemini login in a Zsh terminal. Authenticate using the browser with the Google account associated with the AI Plus subscription. Select the authorized account in the CLI. Attempt to run a prompt using the Pro model. Expected Behavior The CLI should recognize the active Google AI Plus subscription, allocate the proper Pro quota, and execute the prompt. Actual Behavior The CLI reports that Pro usage is at 100% and refuses execution. It appears the backend is returning a Free Tier token with a hardcoded 0 limit for Pro access, trapping the user in a locked quota state. Troubleshooting Attempted Cleared environment variables to prevent workspace conflicts. Attempted Incognito browser routing (resulted in "Access blocked: auth error"). Configured local udev rules (/etc/udev/rules.d/70-snap.google-sdk.rules) for Titan Key to bypass the WebAuthn loop. Downgraded CLI from v0.41.2 to v0.41.1 to bypass known background task quota bugs. Issue persists. Support Request Please review the backend quota flag for this account and verify why the CLI OAuth callback is failing to inherit the AI Plus subscription entitlements.