Authorization death by 1000 clicks

Where does the bug appear (feature/product)?

Grok Bot

Describe the Bug

I have a Mac mini that wa fully set up for openclaw and is a full service computer for developing via coded programs and other things. When I interact on the Mac mini grok bot - it executes - only occasionally asking for permission. When I do the same request from the IOS grok bot - I get 10000 approve once requests, no always approve options and it is harming my workflow and very frustrating. it seems like this just started in the last day or 2.

Steps to Reproduce

It happens over and over and over again

Expected Behavior

I have asked the main agent and the bu agents to stop this and do always approve and keep getting told it is not a iOS feature or some other nonsense like that. These are the SAME AGENTS and it should work no matter how I input the prompt.

Operating System

MacOS

Version Information

Grok Bot IOS Grok Bot Mac OS

Additional Information

This is frustrating enough - I would go back to openclaw vs death by 1000 clicks

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey @Hermione_Jojoclaw, thanks for the report!

What you are seeing is how approvals currently work across the two apps. The “always allow” control for actions on your Mac mini lives in the desktop app on that machine, not in the iOS app. On the phone, each action can only be approved once, and those one-time approvals are cleared whenever you send a new message, which is why it keeps asking.

To fix it:

  1. On the Mac mini, open the Grok Bot desktop app.
  2. Open Settings and find Execution on Local Computer.
  3. Set it to Always allow for that machine.
  4. Keep the desktop app running on the Mac mini, since it re-applies this setting whenever it reconnects.

Once that is set, requests you send from the iOS app should run on the Mac mini without asking each time. If a permission card still shows up on the desktop, choosing Always allow on the card also makes it stick.

Please also make sure both apps are up to date. There was a recent issue where an existing Always allow setting was not being honored, and that has been fixed.