Snapshots

When a Buildprint agent works on your app, it operates on a snapshot — a point-in-time view of your app’s logic. Understanding how snapshots work helps you avoid surprises when collaborating with agents.

How snapshots work

When an agent starts a conversation or syncs your app, it takes a snapshot of your Bubble app’s current state. This snapshot includes your database schema, workflows, pages, and settings at that exact moment.

From that point on, the agent works from this snapshot. It tracks every edit it makes on top of it, so it always knows the current state of the app — as long as the changes came from the agent itself.

What the agent can and cannot see

The agent sees:

• The initial state of your app when it last synced

• Every change it has made since that sync

The agent does not see:

• Changes you make directly in the Bubble editor

• Changes made by other collaborators or agents on the same branch

This means if you edit something in Bubble while an agent is working, the agent won’t know about it. It will continue working from its own snapshot, which could lead to conflicts or overwritten changes.

Keeping the agent in sync

If you make changes outside of the agent and want it to see them, ask the agent to sync. This refreshes its snapshot so it picks up your manual edits.

You should sync whenever you:

• Make changes directly in the Bubble editor on the same branch

• Have another collaborator push changes to the branch

• Want the agent to work with the latest version of your app