I was thinking something very obvious and straight-forward. Like in the Versions page, toggles for read and write. BP would honor those flags.
It would more likely be conversation level
I donât want you to start a conversation and set off the agent and come back annoyed in 30 minutes when you realise that you didnât re-enable editing on that branch!
buildprint was able to schedule API workflow on a list of API types and it actually worked 
Like, the batches are successfully passed through to the scheduled workflow and accessible inside it as âthis batchâs Xâ etc
@boston85719 youâll love this
Thatâs neat. What bubble needs to do is allow parameters of backend workflows be an api object type.
Well, from what I can tell, they already do - itâs just soft-disabled. But it works, you just canât select the type from the params dropdown. If I had to guess, itâs for performance reasons of some sort.
@nick.carroll I know youâre working on API connector, maybe you know the answer 
Okay, I see now. The point was there is no good reason bubble can not implement having api objects as a parameter because if we just reference the ID of the object type as a parameter it actually works and accepts them. Itâs just bubble has not implemented in the UI of the dropdown for parameter types the list of api objects.
Yes, @nick.carroll as team is doing things on APIs, please release this functionality of selecting api object types as backend workflow parameters.
Hi George, would love to join the beta
Very interesting.
I wonder what other âweirdâ unsupported things might AI editing insert into a Bubble app unbeknownst to us and cause strange problems down the line? Thereâs an argument to be made that even the visual UX editor has things like this (e.g. certain conditions can only be copied from elements into workflows and they work fine) but AI editing opens up a whole new set of unknowns.
Ya, when we find stuff like this we improve Buildprint to stop it happening in future as it may not be officially supported 
I do wonder about things that might not be immediately apparent through the editor. If something can slip through the linter and the issue checker and just silently sit there for a while⌠Kind of spooky to think about.
I know itâs an edge case (and unlikely one at that) but Iâm a tail risk kind of guy.
On the flip side, as models continue to improve and you continue to add to the system prompt + your programmatic guardrails, I guess the product itself can scan for and fix these types of issues as effectively as it can create them.
The engine which processes app JSON into code is entirely client side, so itâs easy to go through and identify problematic areas.
But for sure thereâll always be stuff to improve and I canât offer any guarantees with Buildprint yet.
Buildprint organised 345 workflows on this page into folders in one shot based on which section of the page the workflows belong to.
Agent spent about 20 minutes doing it.
It didnât even take a shortcut like grouping them by event type or action or something.
Theyâre genuinely semantically organised!
Maybe something like that.
A simple example of list operators not currently supported in privacy rules, but that can be enforced.
Yeah good example! Did you do this with Buildprint tho
No hahaha, I just created the expression in a group element (with the final part as âCurrent Userâ), then copied it to the privacy rules and changed the final part to âThis userâ.
I was gonna say, we already check for stuff like this 
Donât scare me like that
I havenât tested if it actually works, but it doesnât seem to be flagged as an issue.
Last night i had BP hunt for financial related bugs on my app and it found a couple. As an experiment I asked it to fix one of them. It did.
The crazy part here, is that I did this at 11pm while in my bed just before going to sleep This is absolutely game changing as means i can view/fix/edit/oversee and plan features on my app from anywhere, on my phone, at a cafe, on vacation, not just the office or laptop. Will save a lot of time.
Tbh .. considering where this is already, and where itâs heading (fast), I wonder if there is even any point in bubble doing their own ai 
BP totally nails it imo and itâs only early beta. Iâd be more than happy with builtprint being a new main tab on the bubble editor. (And itâs logs page can also replace bubbles) I feel like itâs trustworthy and built right, with attention to detail and care. They would HAVE to put George and his team in charge of entire AI department tho for quality control.
Bubble could then put their money & time into other essential areas instead.
Not sure if bubble or George would actually want this, but hey, nice thoughtâŚ
Yeah thereâs actually a lot of weird little things that slip in or regardless of ai, just from native bubble itself, which is a bit concerning.
Infact buildprint can actually HELP identify them. For example my app had a load of workflows that were pointing at folders that no longer existed. Teeny bubble bugs sitting there unnoticedâŚâprobably" harmless⌠
Regarding expressions, there are several cases where this can be done (not recommended as they are not ânatively supportedâ).
Things like hover actions that cannot be natively used at the event or action level, but can be created in elements and then copied as conditionals to events and actions.
Other things like actions not supported, for example the Animate an element action that cannot be natively set for a Reusable Popup, but it can be set by converting a âShow/Hide an elementâ into Animate an element action, and it is not flagged as an issue. And so on.
That said, even though this is possible, I strongly advise against using it or relying on this behavior, as it could break at any moment.
@georgecollier, did you make sure to prevent similar things from happening?