Base44 Superagents Now Need Approval Before Any Payment
Base44Base44 Superagents now stop when their browser reaches a pay button, instead of clicking it. Paying needs its own approval. The click only goes through if the button, the amount and the site still match what the user approved.
Key Takeaways
- Superagent browsers now stop at the pay button instead of clicking it automatically.
- Paying needs its own approval, separate from the approval for the surrounding task.
- The click proceeds only if the button, amount and site still match what the user approved.
- A changed amount or a different site breaks the match, which blocks a mismatched payment.
- The change targets the highest-risk action a browser-controlling agent can take.
- Agents can still handle the rest of a checkout flow, so the user keeps the automation but not the unattended spend.
A pause at the pay button
Base44 changed how a Superagent's browser behaves when a task leads to a payment. When the browser reaches a pay button, it now stops instead of clicking. A Superagent can still navigate a checkout flow, but it can no longer complete the purchase on its own.
Approval is separate and specific
Paying requires its own approval, distinct from the approval given for the task as a whole. The click only goes through if the button, the amount and the site still match what the user approved. If the page shows a different amount or sits on a different site, the match fails and the payment does not proceed.
Why it matters
Superagents can control a browser and act in the user's accounts. Money is the highest-stakes action in that setting. Binding approval to the exact button, amount and site limits the damage from a mistaken or manipulated page, and it keeps the user in control of spending while the agent handles the rest of the work.