openclaw "user" browser keeps needing approval

[eager temple]

openclaw "user" browser keeps needing approval

[sly wadi]

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

[safe iron]

That profile="user" path is the Chrome DevTools MCP existing-session attach, so some approval is expected. The docs explicitly say to use it only when you need the signed-in browser and the user is there to approve the attach prompt.

Two important bits:

• If you want no prompt, use the managed openclaw browser profile instead.
• If you mean it asks on every single use, that is not usually expected. I checked current code, and the Chrome MCP session is cached in-process, so repeated prompts usually mean the attach session is getting torn down.

Most common causes:

• Gateway restarted
• Chrome/Brave/Edge got closed
• remote debugging is not staying enabled
• using built-in user for the wrong browser/profile, instead of a custom existing-session profile with userDataDir

Can you paste these first:

openclaw --version
openclaw status
openclaw browser --browser-profile user status
openclaw browser --browser-profile user tabs

Also check the browser’s inspect page and keep that browser open:

• Chrome: chrome://inspect/#remote-debugging
• Brave: brave://inspect/#remote-debugging
• Edge: edge://inspect/#remote-debugging

Docs:

• https://docs.openclaw.ai/tools/browser#existing-session-via-chrome-devtools-mcp
• https://docs.openclaw.ai/tools/browser-login
• https://docs.openclaw.ai/help/faq