In Grok Bot, Auto-review keeps showing approval cards for the same trash tool after the user already gave standing approval in chat and after an Always allowed rule was created for that tool. A later similar action still arrives as Allowed once and pops another card.
Expected: once Always allowed exists (or standing approval was given), same-class agent trash actions should not interrupt with more cards.
Actual: cards keep appearing.
Product: Grok Bot.
Steps to Reproduce
Give standing approval in chat, create an Always allowed rule for the same trash tool, then perform a similar trash action. Another approval card appears.
Hey, thanks for the detailed report. This is a known issue we’re tracking. The Always allow button saves the rule as a text instruction, not as a strict per-tool permission. Because of that, Auto-review might treat the next similar action as outside the rule and show the card again. That’s why you’re seeing a new prompt for the same trash action.
As a temporary workaround, a broader manually written rule usually works better. In Grok Bot: Settings > Auto-review > Auto-review Rules, in the When Grok Bot wants to field enter something like move emails in my Gmail to trash, set It should to Allow automatically, then click Add Rule.
The rules list has a size limit and evicts the oldest rules when it fills up, so it’s worth deleting the narrow trash rules that were added via Always allow so your new broader one doesn’t get pushed out. Also note that if rules conflict, Ask first takes priority.
More on approvals:
I’ve shared your case with the team. I’ll post here if there’s an update.
Removed the narrow Always allow text instruction that was saved for the Gmail Multi trash_email tool. Added a broader manual Auto-review Allow rule: move emails in my Gmail to trash.
Will retest the same Email trash class on the next real pass and report if the card still appears. LinkedIn send allow rules left alone.
Appreciate the diagnosis that Always allow saves as a text instruction rather than a strict per-tool permission.
Great that you tried it. A broader rule usually holds up better than narrow Always allow entries, so this should reduce repeat cards for trash actions.
Let me know how the retest goes on the next real run. If a card for the same class still shows up, post here and I’ll pass the details along. For now we’re keeping an eye on this issue, but I can’t share an ETA for strict per-tool approval yet.