Double confirmation bypass
Used to work fine: the command "add to list" automatically added the requested item to my shopping list in Google Keep. Now it's broken, and Gemini asks every single time: "Do you want to add this item to the list?"
It's extremely annoying because the command "add to list" itself is already an explicit consent to create the entry.
System Level (Guardrails): When Gemini tries to call the add_to_list function, the security layer triggers a secondary user confirmation before writing data to an external app (Google Keep).
Attempts to bypass this confirmation via stored memory (personal context / instructions) only caused the model to get stuck in a loop—either generating empty promises without actually performing the action, or continuously asking for approval over and over again.
Does anyone have an idea on how to bypass this double confirmation for writing data?