gemini-cli - 💡(How to fix) Fix [Bug]: Authentication fails with "automated queries" security block during login [2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
google-gemini/gemini-cli#25270Fetched 2026-04-14 05:56:21
View on GitHub
Comments
2
Participants
3
Timeline
12
Reactions
14
Author
Timeline (top)
cross-referenced ×3labeled ×3subscribed ×3commented ×2

Error Message

I am unable to complete the login process for the Gemini CLI. When initiating the authentication flow, Google's security filter interrupts the request, preventing the OAuth process from completing. The error page states: ".. but your computer or network may be sending automated queries. To protect our users, we can't process your request right now"

Code Example

> /about
# paste output here
RAW_BUFFERClick to expand / collapse

What happened?

Description: I am unable to complete the login process for the Gemini CLI. When initiating the authentication flow, Google's security filter interrupts the request, preventing the OAuth process from completing. The error page states: ".. but your computer or network may be sending automated queries. To protect our users, we can't process your request right now"

I am being locked out of the Gemini CLI authentication process by an "automated queries" security intercept. I want to emphasize that no automated scripts, scrapers, or high-frequency tools are being used. I am simply a developer working manually on code within my local environment.

What did you expect to happen?

works well

Client information

<details> <summary>Client Information</summary>

Run gemini to enter the interactive CLI, then run the /about command.

> /about
# paste output here
</details>

Login information

No response

Anything else we need to know?

No response

extent analysis

TL;DR

The Gemini CLI login process is being blocked by Google's security filter due to suspected automated queries, and a workaround or configuration change may be needed to complete the OAuth process.

Guidance

  • Verify that the Gemini CLI is configured to use a user-agent that identifies itself as a legitimate client, rather than a script or automated tool.
  • Check the network configuration and ensure that the request is not being proxied or modified in a way that triggers Google's security filter.
  • Consider adding a delay between authentication requests to avoid triggering the security filter.
  • Review the Gemini CLI documentation to see if there are any recommended settings or workarounds for this issue.

Example

No code snippet is provided as the issue does not imply a specific code-related solution.

Notes

The exact cause of the issue is unclear, and it may be related to the specific network or environment configuration. Further investigation and experimentation may be needed to determine the root cause and find a reliable solution.

Recommendation

Apply workaround: Implement a delay between authentication requests or modify the user-agent to identify as a legitimate client, as this may help avoid triggering Google's security filter.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING