What to review before Bubble's Agent 2 edits your live app
Bubble's release notes for 7 October 2026 say "Agent 2 is out of beta and available on every app, including existing apps." That means it can edit an app with real users and real data, so treat its changes as you would a contractor's. Work on a branch, take a savepoint first, then review six things before you merge: privacy rules, the workflows it touched, workload unit impact, the expressions it rewrote, new data and plugins, and behaviour as real user roles.
What Bubble has said
The Bubble release notes list Agent 2 under Features on 7 October 2026. Bubble also says Agent 2 runs the issue checker in the background while it builds. An issue checker catches errors, but it cannot know what you meant to protect or what a change should cost, so the judgement stays with you. Everything below is our own advice, based on repairing Bubble apps.
Before you let it edit
- Make a copy to work on. If your plan includes branches, make a branch and do the work there rather than on the version your customers use. Whatever your plan, create a savepoint of the version you are about to change, with a name you will recognise, such as "before Agent 2, 14 Nov". A savepoint is your way back.
- Write down the baseline. Note your current workload unit use from the App metrics for a normal week, and run the issue checker so you know which warnings were already there. You cannot judge a change without a starting point.
- Ask for small jobs. One change per request is far easier to review than ten, and if one goes wrong you can undo it without losing the others. Say in the request what must not change, such as privacy rules, payments and plugins.
What to review afterwards
- Privacy rules. Open every data type the agent created or touched. Check that each has a rule, that the default rule for everyone else grants little, and that a search or a Data API call cannot return another user's records. Test as a logged-out visitor and as an ordinary user. Rules that are too tight break things too, so read our guide to privacy rules hiding search results if lists go empty.
- The workflows it touched. Open each one and read it line by line. Look for new or changed conditions, an action that now ignores privacy rules, a backend workflow that is newly exposed as an API workflow, and any workflow that schedules itself or triggers another that comes back around. Loops cost money fast, and our guide to a recursive workflow loop explains how to stop one.
- Workload unit impact. Compare App metrics over the same kind of week. The usual culprits are searches inside searches, large lists filtered on the page instead of in the search, and repeated searches in a workflow. See workload unit spikes from nested searches for how to find and fix them.
- Expressions it rewrote. When a field is renamed, replaced or deleted, expressions that used it can break or quietly return nothing. Search your pages and workflows for red or empty dynamic values, then check the issue checker. Our guide to broken expressions after deleting a field walks through it.
- New data, options and plugins. Check for new fields, data types, option sets and installed plugins. A plugin you did not ask for is a question to answer before you merge. Check that no API key or secret has been placed somewhere visible.
- Behaviour as real roles. Click through the main flows as a logged-out visitor, a normal user and an admin. Pay for something in test mode if you take payments. Check emails and any connected tools.
Merge, then keep the savepoint
Merge only when the review is clean, and keep the savepoint for at least a week of normal traffic. If a cost or a rule problem shows up late, restoring or comparing against it is far cheaper than finding out what changed from memory. Tell your team what changed, and note the savepoint name in your change log.
Want a second opinion?
Our AI-Built App Audit is a report-only review of an app built with an AI app builder, tested as real user roles, with findings ranked by risk and a fix plan. If Agent 2 has done much of the building, ask us whether it fits your app. For a narrower check, see the Privacy Audit, and for a bill that jumped, Workload Unit Surgery. Prices are on each page.
Sources
- Product Updates and Release Notes, entry "Agent 2", Bubble, 7 Oct 2026
- Introducing Agent 2 and the Bubble MCP, Bubble blog, 6 Oct 2026