Issue Station
Sign In
Tools hereToolbox

gemini-cli - ✅(Solved) Fix After v0.37.0 update, YOLO is asking for approval. [1 pull requests, 3 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#25015•Fetched 2026-04-10 03:45:26
View on GitHub
Comments
3
Participants
3
Timeline
8
Reactions
1
Author
EricDeng1001EricDeng1001
Participants
EricDeng1001EricDeng1001scidominoscidominovini826vini826
Timeline (top)
labeled ×4commented ×3unlabeled ×1

PR fix notes

PR #25341: fix(core): prevent YOLO mode from being downgraded

Description (problem / solution / changelog)

Summary

Prevents YOLO mode decisions from being downgraded to ASK_USER when a shell command is evaluated as dangerous by heuristics.

Details

In packages/core/src/policy/policy-engine.ts, the policy engine previously overrode decisions to ASK_USER if this.sandboxManager.isDangerousCommand(parsedArgs) returned true, even when YOLO mode was active. This change ensures that YOLO mode (where the user expects autonomous execution) preserves the ALLOW decision for dangerous commands. Added a test case should return ALLOW in YOLO mode for dangerous commands due to heuristics override.

Related Issues

#25015

How to Validate

  1. Run the test suite: npm run test -w @google/gemini-cli-core -- src/policy/policy-engine.test.ts
  2. Start the CLI in YOLO mode and attempt to run a command that triggers the dangerous command heuristics. Verify it runs autonomously without asking the user.

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

  • packages/core/src/policy/policy-engine.test.ts (modified, +33/-0)
  • packages/core/src/policy/policy-engine.ts (modified, +7/-0)
  • packages/core/src/tools/shell.ts (modified, +5/-0)

Code Example

> /about
                                                                                                                     │
│ About Gemini CLI                                                                                                     │
│                                                                                                                      │
│ CLI Version                              0.37.0                                                                      │
│ Git Commit                               352bbe149                                                                   │
│ Model                                    gemini-3-pro-preview                                                        │
│ Sandbox                                  no sandbox                                                                  │
│ OS                                       win32                                                                       │
│ Auth Method                              Signed in with Google (gantinus@gmail.com)                                  │
│ Tier                                     Gemini Code Assist in Google One AI Pro
RAW_BUFFERClick to expand / collapse

What happened?

YOLO is not working anymore. I use ctrl + Y enable YOLO and agent is still asking for approval.

What did you expect to happen?

No approval should be asked.

Client information

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

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

> /about
                                                                                                                     │
│ About Gemini CLI                                                                                                     │
│                                                                                                                      │
│ CLI Version                              0.37.0                                                                      │
│ Git Commit                               352bbe149                                                                   │
│ Model                                    gemini-3-pro-preview                                                        │
│ Sandbox                                  no sandbox                                                                  │
│ OS                                       win32                                                                       │
│ Auth Method                              Signed in with Google ([email protected])                                  │
│ Tier                                     Gemini Code Assist in Google One AI Pro
</details>

Login information

No response

Anything else we need to know?

No response

extent analysis

TL;DR

  • The issue with YOLO not working and still asking for approval after enabling it with ctrl + Y may require checking the configuration or settings related to YOLO and approval processes.

Guidance

  • Review the Gemini CLI documentation to ensure that ctrl + Y is the correct shortcut for enabling YOLO and that no additional steps are required.
  • Check if there are any specific settings or configurations in the Gemini CLI that need to be adjusted to prevent approval requests when YOLO is enabled.
  • Consider running the /about command again after attempting to enable YOLO to see if there are any changes in the output that could indicate why approval is still being requested.
  • Look into the Gemini Code Assist in Google One AI Pro documentation to see if there are any known issues or limitations related to YOLO and approval processes.

Notes

  • The provided information does not include specific details about the YOLO feature or its configuration, which might be necessary to troubleshoot the issue effectively.
  • The issue might be related to the specific version of the Gemini CLI (0.37.0) or the model being used (gemini-3-pro-preview), but without more information, it's difficult to determine.

Recommendation

  • Apply workaround: Try to find an alternative method to enable YOLO or adjust the approval settings, as the current method is not working as expected.

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…
#runtime error#dependency conflict#environment setup#docker error#permission error

Still need to ship something?

×6

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

Back to top recommendations

TRENDING