gemini-cli - 💡(How to fix) Fix bug: 403 PERMISSION_DENIED error when using Google OAuth or API Key via CLI [1 participants]

I am consistently receiving a 403 PERMISSION_DENIED error when executing any command in the Gemini CLI. This issue started suddenly about 24 hours ago. Prior to this, the CLI was working perfectly with the same setup Error Message : ✕ [API Error: [{ "error": { The error appears immediately after the request is sent Tried using a freshly generated API Key from AI Studio (same error: 403 Forbidden or Your project has been denied access)

TL;DR

The most likely fix is to review and adjust the API key or authentication settings, as the 403 PERMISSION_DENIED error suggests a permission issue.

Guidance

• Verify that the API key is correctly generated and applied, considering the recent changes or updates in the AI Studio or Gemini services.
• Check if there are any regional restrictions or access limitations for the Gemini CLI in Pakistan (Karachi), as the web interface is working fine.
• Try using a different authentication method, such as switching from Google Login to API Key or vice versa, to isolate the issue.
• Review the Gemini CLI documentation for any specific requirements or updates related to authentication and permissions.

Example

No code snippet is provided as the issue is related to authentication and permissions, and no specific code changes are implied.

Notes

The issue may be related to a recent change in the Gemini service or AI Studio, and it's essential to review the documentation and release notes for any updates on authentication and permissions. Additionally, regional restrictions or access limitations may be a contributing factor.

Recommendation

Apply a workaround by trying a different authentication method or reviewing the API key settings, as the root cause of the issue is likely related to permissions or authentication.