Announcing Buildprint AI: Build on Bubble with Claude Code and Codex šŸŽ‰

I’ve just sent off a first round of invites to the Buildprint AI editing beta.

If you’re interested, please reply below (I’ll struggle to keep track of DMs). If your name / profile is obvious then I’ll be able to find your workspace and grant you access (though I’ll be doing it gradually just so I can deal with any issues as they arise :slight_smile: )

still interested :slight_smile: How do we know if we are on that beta?

you received a message on X

@georgecollier would love beta access please :hand_with_fingers_splayed:

Would love beta access @saviorabrams on X

Blessup for the amazing system you’ve Built George..
Really happy about the upgrades! :clap:

Definitely love to get access to the AI editing beta. :saluting_face:

I definitely want to try this out soon, but could you clarify if you have an option like this?

Screenshot 2026-02-25 194551

I’m assuming you personally have the ability to see anything that’s contained in our app’s JSON after it’s been filtered/extracted (or data if we enable access to data).

Knowing George, he probably has access to our app json without our permission too :wink:

I recall him doing some crazy things during a DevDay presentation and his app audit service.

We’re constrained by the Bubble collaborator permissions and additionally restrict it so it can’t access private API keys or plugin values. There are docs on the permissions and privacy options tho

So the user session you create is for your account?

Our collaborator does the edits. We don’t have access to your account.

@georgecollier My app has been in production for 6 years and I’m learning new things about it thanks to this, it’s absolutely fantastic. Instantly a must-have for any bubble app. Would love beta access if available.

Gave the beta a test-run today and let it have a go at a couple of tasks - conclusion: absolutely blown away.

Task 1: I needed to duplicate a load of buttons and their respective workflows/actions to use them as new buttons on a newly built side-panel. To avoid workflow duplication I asked for it to make the button workflows into custom events instead, first, so they could be triggered from multiple other places without duplication. It did it. I manually checked the work - flawless :exploding_head:

Task 2: this one i’ve been putting off for MONTHS… 147 workflows sat in ā€œuncategorizedā€ folder. A real chore to manually move them into sensible folders. I asked BP to do it and gave it the desired folder naming convention… it moved them into my existing folders and created new folders where needed. 1 go. Flawless. :exploding_head:

Can’t praise this thing enough. Genuinely exciting.

(Model being used is Claude Opus 4.6 btw)

We are approaching the era of self driving Bubble apps.

I’ll be releasing a Buildprint API so you can trigger agents programatically.

That means that you could have a bug report form in your Bubble app, which triggers a Buildprint agent to investigate, explain, and fix it.

So that all you need to do is review its work and deploy the fix.

PSA: We now account for a significant amount of Bubble logs requests so are throttling requests whilst they’re doing some planned backend work (that will improve logs for everyone, whether you use Buildprint or not). If you see log sync fall behind, that’s why.

I’m interested, George! Amazing work

Is there a way to lock BP down to a dedicated branch without having to include it in the prompt? I know it does save points but I think if it can be fenced-in to a specific branch, that would alleviate the current ā€œopenclaw phobiaā€.

Not yet, possibly in future with formal plan mode etc

I will add the ability to add your own system prompt, behaviour guidelines, style guidelines etc for each project too at some point. I just want to make the UX nice (so it autopopulates style guidelines based on app naming convention UI etc rather than you just typing it)