gemini-cli - ✅(Solved) Fix CLI constantly get stuck for 15 minutes or more on a simple implmentation plan review [1 pull requests, 1 comments, 2 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#25110Fetched 2026-04-11 06:31:31
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Timeline (top)
labeled ×3commented ×1cross-referenced ×1

PR fix notes

PR #25317: feat(core): implement silent fallback for Plan Mode model routing

Description (problem / solution / changelog)

Summary

Implement silent fallback for Plan Mode to ensure an uninterrupted user experience when Pro models are unavailable or inaccessible.

Details

This PR introduces a "Unified Injection" approach to enforce silent fallback when the system is in Plan Mode. By intercepting the ModelPolicyChain resolution in resolvePolicyChain, all fallback actions are overridden to 'silent' if ApprovalMode.PLAN is active. This ensures that failures in the primary planning model (Pro) automatically trigger a transition to the next available model (Flash) without interrupting the user with prompts or getting "stuck".

  • Exported SILENT_ACTIONS from policyCatalog.ts.
  • Refactored resolvePolicyChain in policyHelpers.ts to apply silent overrides.
  • Added unit tests in policyHelpers.test.ts verifying silent fallback for both legacy and dynamic routing paths.
  • Updated docs/cli/plan-mode.md to document the new behavior.

Related Issues

Closes https://github.com/google-gemini/gemini-cli/issues/25110

Pre-Merge Checklist

  • Updated relevant documentation and README (if needed)
  • Added/updated tests (if needed)
  • Noted breaking changes (if any)
  • Validated on required platforms/methods:
    • MacOS
      • npm run
      • npx
      • Docker
      • Podman
      • Seatbelt
    • Windows
      • npm run
      • npx
      • Docker
    • Linux
      • npm run
      • npx
      • Docker

Changed files

  • docs/cli/plan-mode.md (modified, +4/-0)
  • packages/core/src/availability/policyCatalog.ts (modified, +1/-1)
  • packages/core/src/availability/policyHelpers.test.ts (modified, +14/-1)
  • packages/core/src/availability/policyHelpers.ts (modified, +48/-36)
RAW_BUFFERClick to expand / collapse

What happened?

I wrote a plan to change few things on a codebase, shared with cli to validate, and it got stuck for 30m try again more 15m with o response at all. Unusable

What did you expect to happen?

Get a response promptly instead of waiting ages with Thinking spinner on the cli, and having nothing done.

Client information

  • CLI Version: 0.36.0
  • Git Commit: 8b1e649c2
  • Session ID: 74070117-6135-4694-9e1b-87ec74791852
  • Operating System: win32 v22.17.0
  • Sandbox Environment: no sandbox
  • Model Version: auto-gemini-3
  • Auth Type: oauth-personal
  • Memory Usage: 397.3 MB
  • Terminal Name: Unknown
  • Terminal Background: #002b36
  • Kitty Keyboard Protocol: Unsupported

Login information

No response

Anything else we need to know?

Plan: Gemini Code Assist in Google One AI Pro

extent analysis

TL;DR

  • The issue may be resolved by retrying the command or checking for updates to the CLI version 0.36.0.

Guidance

  • Verify if the issue persists across multiple attempts to validate the plan using the CLI.
  • Check for any available updates to the CLI version 0.36.0, as updating may resolve the issue.
  • Consider testing the plan validation in a different environment or setup to isolate if the problem is specific to the current configuration.
  • Review the plan itself for any potential issues or complexities that could be causing the CLI to hang.

Notes

  • The provided information does not specify the exact commands or steps taken, which could be useful for further troubleshooting.
  • The issue might be related to the specific plan, the CLI version, or the environment in which it's being run.

Recommendation

  • Apply workaround: Retry the command and consider testing in a different setup to see if the issue persists, as this allows for immediate troubleshooting without waiting for potential updates.

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