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

Fast mode

Fast mode is now available for Cursor and OpenAI models.

Any timeline to share on custom domains for Extensions @georgecollier ?

Nah won’t be for a few weeks

I’m putting together an extension, and just hit a 31 day roadblock. Reported it, but was hoping there’s a way for you to lift the limit @georgecollier . Agent explained it like this:

Isolating the bug above took many publish attempts, and the app has now hit an extension-publish limit reporting a retry-after of roughly 31 days. That is my error — I should have suspected a per-publish budget before bisecting that aggressively. The Worker code and schema are finished and correct; they simply cannot be deployed until that limit clears or is lifted.

Wait an hour, it looks like there’s a bug showing the retry-after in seconds rather than milliseconds which makes the agent think 31 days

But rate limits are 5 per minute, 30 per hour, and 200 per day.

I strongly recommend using the inbox sidebar layout by the way

Been experiencing this a lot over the past couple days:

Agent won’t restart once that’s happened, so it won’t let me file the bug report. Side chats also stay in ā€œPlanning next stepsā€ until that same error appears.

There’s a CLI performance issue on certain commands in certain cases which I’m working on atm and will resolve it in future. I’ll update the thread when it’s deployed

bubblescript cli when?

I’m wondering if this will mean it will use less agent runtime in buildprint. I’ve hit my 20 hours already and I still have another 14 days to go until it renews. :rofl:

I guarantee you agent runtime is a lot cheaper than model fast modes! I just added fast mode for people who want to burn their limits.

Agent runtime isn’t free for good reason btw lmao

Wow ! Yeah I see what you mean!

Gandalf The White vs The Night King - Battles - Comic Vine

2 Likes

obesssion

Need a quick sanity check. I’m a long-time Bubble builder, not a coder, and I’ve been experimenting with prototyping pages via extensions.

I put together a basic training page prototype, had it build out onto my test branch, tested it, and deployed to live.

Everything works fine, but looking at my extensions tab, the UI states that it ā€œStatus is TEST and LIVE.ā€

And I can’t seem to delete it?

I assumed the extension was strictly for generating the prototype, which then gets translated into native Bubble elements. What is actually ā€œliveā€ from the extension side of things? Is it just notifying me that the implementation made it to production, or is the prototype itself hosted/running in parallel?

Any insight into how the extension interface handle this under the hood would be much appreciated!

Extension docs are here: Introduction to Extensions | Buildprint | Docs

Extensions are separate to your Bubble app and basically little bits of custom code. Maybe you would call them an ā€˜artifact’ in other agents.

If you click into your extension, you’ll see a URL where you can open it and preview it.

Today’s update is a new world for large Bubble apps! Thanks @georgecollier :heart_eyes:

Have seen a couple of the errors below today when trying to apply changes. Is this a transient try later error?

However, Bubble did not accept the apply. Three attempts returned an indeterminate transport response, and repeated syncs confirmed the Test editor counter remained unchanged. Therefore, these changes are not yet in Bubble. The validated draft is preserved and ready to retry once the Buildprint/Bubble connection recovers.