Nevermind theyāre shipping MORE than Iād figured out
Check in again tomorrow haahhaha
Weāll be releasing a /upgrade skill which lets Buildprint upgrade your app to remove workarounds and take advantage of the new features!
Huh? Donāt think you understand BP.
no idea what āBPā is
Buildprint: your screenshot shows bubbleās AI agent running from the Live āJust Shippedā ā BP (Buildprint) allows you to use any compatible AI. This allows bubble devs to benefit from advances in any AI family rather than just bubbleās! Not sure if youāre being sarcastic?
Haha
Had a few questions already from people about how Buildprint tests differ from Bubbleās alpha test preview:
- Buildprint tests automatically update and resolve themselves when your app changes
- Tests support both screenshots and videos
- Tests can be run on deploy or branch merge
- Tests can use any user in any branch
Iām sure Bubbleās will develop further in their alpha - Buildprint walks so Bubble can run!
That aside, these releases are all very good from Bubble.
Weāll be releasing /upgrade skills which automatically update your Bubble apps with the latest features and remove workarounds. Stay tuned!
george buildprint is dead
long live george buildprint
Bubble didnāt build an LLM, they leverage the same models others do as well, this is why the announce improvements after the LLM new models are releasedā¦but, I donāt think at the moment they give users choice in which to use, likely as they subsidize it.
Surely theyāll let people choose their own soon enough.
Is there a bug affection automations? I tried setting up a manual automation to test a new automation, and set it to email and another with webhook. Neither are going through, when I click run in the dashboard. Iāve been waiting for like over an hour.
Email incorrectly sent out to 38 users to upgrade dedicated instance
Hey everyone!
Iām aware of an email notification issue today relating to an update to observability weāre making. To support this update, you need to upgrade your dedicated instance by June 5th.
We notified users by email for each dedicated instance, in an email like this (with the app name):
The email only includes the project name, but may be confusing if it was a project name youāre not familiar with.
This email was intended to only be for members of the project. However, in a small number of cases affecting 38 users, it went to members of the workspace. Affected users will receive an email shortly.
Ordinarily, we have safeguards in place to prevent access between projects for users in the same workspace. However, these are not as strict for workspace members as they are for project members. If you had a workspace member (rather than āguestā, as intended is intended for external users that are not part of your company) then they may have received the email for all dedicated instances in the workspace.
Going forward, weāll make this clearer in the documentation. Project vs workspace permissions can be a bit confusing with Buildprint at the moment and we donāt have a single view to manage user permissions in the both workspace and its projects (weāll add this shortly). Agencies using Buildprint should only ever invite external users as āguestsā to projects.
@georgecollier Errors also appear when trying to fork a conversation. (The same browser console errors appear when I try to fork regularly, as well as click this button.)
Thanks for the clarification!
Yes, I mean, for now, I love the control of BP being able to use almost unlimited GPT 5.5 Codex with my Pro account.
Buildprint gets latest Bubble features, no longer overwrites manual changes, faster log sync
Buildprintās just received a big batch of updates.
Better log sync
- non-dedicated apps are being moved onto a new log sync pipeline today. Logs have become delayed due to rate limits, but will recover across the course of the day. Your logs will sync much faster (generally within a couple of minutes)
- Dedicated server users should update to the latest version of Bubble in their editor, else logs will stop syncing from June 6th.
- We will soon be releasing observability off the waitlist, and will also be rolling out logs for all Bubble branches, not just live version.
Latest Bubble features
- all new Bubble features are supported, including global expressions, styles as conditional properties, trigger custom event from backend workflows, reusable element property descriptions
Better collaboration in the editor
- Buildprint will no longer overwrite changes you make in the Bubble editor that itās not aware of. When it applies changes, it will be notified if its local workspace is out of sync and will initiate a sync itself to ensure it is up to date. Note that if you want Buildprint to see your changes, you should still tell it to sync itself.
Lower latency on Buildprint web
As a result of the significant changes and improvements to Buildprint, weāve added a version bump for Buildprint web conversations. Youāll need to fork your conversation to continue. Sorry for the inconvenience!
Fixes and improvements
- fixed filters in data tab returning no results when filtering by an associated data type
- improved backend workflow issue checker
- added run as user (from specific page)
- fixed bug with workflow actions not being able to be mutated in place
- fixed bug with large writes being rejected by Bubble
- fixed bug with users using SSO login not having email displayed in data explorer
- improved performance of data explorer
- Issue forking chats in progress @Chana
- improved agent reliability in Buildprint web (affects code reviews + automations too)
Hey George ā this isnāt the first time this happened, so Iām feeling this would be a nice QOL improvement: can you put a kill switch on chats somewhere to prevent instances where the stop button is not available? Perhaps on the chat column-bar itself? This has been running for an hour, wonāt ācontinue in new chatā for some reason and I have no way of stopping it. I archived the chat but that doesnāt do anything either.
It is actually killed, itās just a UI bug and a fix is deploying for it shortly 
So the agent isnāt working and eating all your tokens!
Itās good when people complain about bugs in the rollouts though, means people are using it 
@georgecollier I had to create a new chat + fork since āBuildprint has been upgraded.ā When I started a chat for the agent to look into a repeating group, this happened for 18+ mins:
What model? And does it reliably happen when forking? Does it happen when starting a conversation fresh (not forked)?
There seems to be a new bug introduced since the update. Itās trying to ask user question but then cancels it and just keeps working away like I cancelled the questions. @georgecollier
