openclaw - 💡(How to fix) Fix Browser approval flow is confusing - users must manually send /approve commands

When trying to use the browser tool (e.g., for Lightpanda browser skill to navigate sites like Royal Road), the system repeatedly requests scope upgrades with different request IDs (e.g., b1657d50-8419-43a9-9501-e7e193e81c1b, 21256ed5-fb77-4912-875b-52e70045e5e4).\n\nUsers must manually send '/approve {requestId}' as a chat message to proceed, but this is not intuitive:\n1. The error messages don't clearly explain how to approve\n2. Users may not know they need to send this as a chat message\n3. The request ID changes frequently, requiring repeated approvals\n\nSuggested improvements:\n- Provide clearer instructions in the error message\n- Consider a more streamlined approval process for browser automation\n- Possibly cache approvals for a session\n- Provide a helper command or UI element for approval\n\nThis creates friction for legitimate browser automation use cases like fetching latest chapter content from web novels.