Ai getting stuck and so many credits burned

Ask us anything
1

I’ve easily burned through a couple million AI tokens from the AI getting stuck while building the requested feature. Can someone give me tips on best practices for prompting the AI to prevent this from happening as often?

I don’t rely on the AI entirely—I want to build my app manually for the most part so I know exactly how it’s built. However, I do use the AI for certain tasks to speed up the design process.

By the way, I’ve never seen anything like this AI. It’s by far the most advanced app builder I’ve ever personally witnessed. However, burning through these credits is starting to burn my wallet! :joy:

1 Like
2

Hi Danny! Glad to hear you’re enjoying the AI so far despite the quick token burn :sweat_smile:

Off the top of my head, I would say: scoping your request is key.

For example, if you need to edit a specific element or section, make sure to select that element or section before prompting the AI so that the AI “scopes” your request properly and doesn’t attempt to change your entire page.

To learn more about prompting WeWeb AI, I’d recommend going through these 3 videos by @Matthew_S’s that give a few prompting tips: