Agent capabilities

Agent can inspect and change your Bubble project, work with database records and logs, manage branches, run tests, and use connected tools.

The exact capabilities depend on the project type, your Buildprint role, the permissions granted in Bubble, the selected branches, and whether the conversation is in Plan or Build mode.

Understand your app

Agent can inspect the permitted structure of your Bubble app or plugin.

It can read and explain:

• Pages and reusable elements.

• Elements, styles, and responsive settings.

• Frontend and backend workflows.

• Data types, fields, option sets, and privacy rules.

• API Connector calls and supported app settings.

• Bubble branches and version history.

You can ask Agent how a feature works, where a value comes from, what a workflow changes, or what could be causing a problem.

Build and change your app

In Build mode, Agent can create, update, and delete permitted parts of your Bubble app.

This includes:

• Creating and editing pages, reusable elements, and UI elements.

• Creating and changing workflows and actions.

• Changing conditions, expressions, styles, and responsive settings.

• Creating and changing data types, fields, option sets, and privacy rules.

• Updating supported API Connector configuration.

• Building and updating Bubble plugins in plugin projects.

Agent can work across several connected parts of a feature. For example, it can add a data field, update a workflow, change the page UI, and test the result as one task.

Work with database records

Agent can read and manage Bubble database records when data access is enabled.

In Plan mode, Agent can search, fetch, count, and analyse records without changing them.

In Build mode, Agent can use the Buildprint CLI inside its virtual machine to:

• Create new records.

• Read and search records.

• Update field values.

• Delete records.

Every data operation targets an app and Bubble environment explicitly. Live uses Live data. Test and custom branches use development data.

Investigate logs

Agent can search and analyse Bubble server logs when log access is enabled.

It can find errors, follow workflow activity, inspect requests and responses, compare behaviour across versions, and connect log events to the relevant app logic.

Agent can also help create queries and monitors for problems you want to track.

Manage Bubble branches

Agent can work with Bubble version control when the connected collaborator has the required access.

It can:

• List and inspect branches.

• Create a branch for new work.

• Compare changes between branches.

• Create savepoints.

• Merge branches when permitted.

• Check the app after a merge.

Agent cannot deploy your app to Live. You remain responsible for reviewing, testing, and deploying changes through Bubble.

Create and run tests

Agent can use Buildprint Tests to check app behaviour in a browser.

It can create tests, add steps and conditions, configure test users, run tests against a Bubble branch, inspect screenshots and other evidence, and investigate failed runs.

Use other Buildprint features

Agent can use other project features as part of a task.

• Open and work from Radar findings.

• Browse and install Components.

• Read project Skills and follow their instructions.

• Work with files attached to the conversation.

• Use connected Linear and Slack context where available.

Use connected MCP tools

Custom MCP connections add tools from other services to new Agent conversations.

For example, an MCP server could let Agent read documentation, query another system, or update an external service. The available actions and permissions come from that MCP connection.

Capability limits

Agent cannot bypass Buildprint roles, Bubble collaborator permissions, branch access, or permissions from a connected service.

Some capabilities are available only for Bubble app projects. Plugin projects do not include app logs, database records, Radar, or browser tests.

Agent can make mistakes. Use Permissions and security to control access, and follow the best practices before merging or deploying important work.