Approval

Grok Bot approval needed stuck

Grok Bot approval needed stuck is usually a card that already timed out, or an Ask first rule that outranks Allow automatically. Rebuilding the computer does not delete that rule.

Read the proposed target before you approve anything. If the card is no longer clickable, cancel it or send a replacement instruction.

Why the native method fails

The native method is to Reset, or to flip Always allow, because a homepage tile still says Approval needed and the bot has nothing in front of you. Staff say that tile is often an approval card that timed out after about 10 minutes unanswered. The tile is supposed to clear when the card expires. When it does not, open the agent and send a short message, or restart the app. Reset would rebuild the computer and can drop unsynced work, and it would not remove an Ask first rule that is still on the account.

The cost lesson records the same precedence from the product: Require Approval outranks Always Allow. A wide rule such as allow everything in the browser does not beat an Ask first rule, including a team rule an admin requires.

Steps

1. Open the card and read the target and the arguments. Approve only if that action is the one you wanted. Official troubleshooting says that if the card is no longer actionable, reject or cancel it when that control exists, send the bot a replacement instruction, and ask it to regenerate the action with the corrected scope.
2. If the homepage tile remains and the bot has nothing pending, use the staff workaround: open the agent and send a short message, or restart the app. Do not click Reset to clear a badge.
3. If the same class of action keeps asking, open Settings, General, Bot, Auto-review. Look for a matching Ask first rule, including team rules. Ask first takes precedence over Allow automatically. Personal auto-review rules live on the current desktop and sync to its Grok Bot computer. Check them again after you switch desktops. A rule you set on the office Mac is not automatically the rule on a home Mac until that sync has happened.
4. A different stuck reminder, the one that says the bot is waiting for help on its computer after login already succeeded another way, clears only when you answer that card or send any chat message. It does not dismiss itself. That card is covered on the waiting-for-login page. Do not confuse it with Auto-review.

Limits

Always allow for local-computer actions is desktop-only, and ExternalShell can still be blocked despite it. Turning it on to escape an approval card can allow local commands you did not mean, without clearing an Ask first rule. iOS cannot set Always allow at all.

This page does not list every team policy an admin can require. If the rule is locked and you cannot see Auto-review change it, ask the admin. Support mail is hi@cursor.com when a card is stuck and the restart plus a chat message did not clear the badge. Include the bot name and the time. Do not include the secret the card was asking for.

FAQ

Related

• Shared computer — Takeover, secrets, and what Reset actually removes.
• Approvals and usage — Require Approval outranks Always Allow.
• Waiting for login — The card that wants you on the computer, not in Auto-review.
• Local computer — Where Always allow actually lives.

Sources

• Official troubleshooting
• Homepage approval tile
• Waiting card does not auto-dismiss