gemini-cli - 💡(How to fix) Fix browser agent tool use requires constant approval in yolo mode [2 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#25872Fetched 2026-04-24 06:13:40
View on GitHub
Comments
2
Participants
2
Timeline
7
Reactions
0
Timeline (top)
commented ×2mentioned ×2subscribed ×2labeled ×1

Code Example

"agents": {
    "overrides": {
      "save_memory": {
        "modelConfig": {}
      },
      "browser_agent": {
        "enabled": true
      }
    },
    "browser": {
      "sessionMode": "existing",
      "allowedDomains": [
        "*.com",
        "*.org"
      ]
    }
  }
RAW_BUFFERClick to expand / collapse

What happened?

I enabled the browser agent with the following json

"agents": {
    "overrides": {
      "save_memory": {
        "modelConfig": {}
      },
      "browser_agent": {
        "enabled": true
      }
    },
    "browser": {
      "sessionMode": "existing",
      "allowedDomains": [
        "*.com",
        "*.org"
      ]
    }
  }

Even when running gemini in yolo mode, I am forced to constantly approve the use of the agent's tools even if selecting to enable tool or all tools for the session.

What did you expect to happen?

I expect the browser agent to work without requiring manual approval.

Client information

  • CLI Version: 0.39.0
  • Git Commit: 398f78dca
  • Session ID: 2596fba2-8c21-41c1-84c2-c4d9b7d27dd3
  • Operating System: win32 v22.22.2
  • Sandbox Environment: no sandbox
  • Model Version: auto-gemini-3
  • Auth Type: oauth-personal
  • Memory Usage: 248.5 MB
  • Terminal Name: Unknown
  • Terminal Background: #0c0c0c
  • Kitty Keyboard Protocol: Unsupported

Login information

Google Account

Anything else we need to know?

No response

extent analysis

TL;DR

The issue might be resolved by adjusting the browser_agent configuration to automatically approve tool usage.

Guidance

  • Review the browser_agent configuration to ensure it is set up to automatically approve tool usage, potentially by adding an autoApproveTools option.
  • Verify that the sessionMode is correctly set to existing and that the allowedDomains list includes the necessary domains.
  • Check the documentation for the browser_agent to see if there are any specific requirements or options for auto-approving tool usage.
  • Test the configuration with a different sessionMode or allowedDomains setting to isolate the issue.

Notes

The provided configuration snippet does not include an autoApproveTools option, which might be necessary to automatically approve tool usage. Without further documentation or information about the browser_agent configuration, it is difficult to provide a more specific solution.

Recommendation

Apply workaround: Adjust the browser_agent configuration to include an autoApproveTools option, if available, to automatically approve tool usage.

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