I am really enjoying the new app builder, and despite the loss of drag-and-drop editing capabilities, I have definitely experienced a net gain in productivity as the AI does a great job executing on my vision.
However, my ability to use the builder is being greatly diminished by its AI credit usage. Even basic tasks, like “Expand this section on the page” can consume 100 AI credits!
To build anything meaningful, I am blasting through the provided 3,000 credits/mo. That balance is typically gone in a day or two. And since the builder cannot forecast credit usage before you submit a prompt, you really just have to take a gamble whether or not you’ll be able to build your app before you run out of credits.
I am using the default model (Opus 4.8).
Is this unusual? Or just par for the course of AI app building in Retool? Would appreciate feedback or tips!
Using the new app builder with the default Opus 4.8 model, even basic tasks (e.g. 'expand this section') can burn ~100 AI credits, quickly exhausting the monthly allotment, and there's a question of whether this is expected or reducible.
AI Response
This is expected behavior rather than a bug: before any prompt runs, the builder pre-loads a large baseline context (resource schemas, source files, function outputs, dependency metadata, and conversation history), and credit consumption scales with reasoning complexity, output size, and total context processed. Several documented practices can meaningfully reduce burn: switch to a lighter model for simple edits (reserve Opus 4.8 for complex, multi-step changes), write precise prompts that name resources/components directly to avoid costly re-tries, and start a fresh thread when the task shifts so context doesn't accumulate. Credit and per-response usage can be tracked under Settings > Plans & Billing (Usage tab) and by hovering the icon below each agent response in the Chat tab.
Sources
Token management for app building | Retool Docs
Explains why baseline context is large and lists concrete ways to cut credit usage—model selection by task complexity, precise prompting, new threads, and usage monitoring. New models for building apps
Staff announcement confirming lighter-weight models (Claude Sonnet 5, the GPT-5.6 family, and Claude Fable 5) are now selectable, supporting the switch away from the default Opus 4.8 for simpler tasks.
The Community Team is testing out a new automation. Let us know if it's helpful (or not) by leaving a , , or . Or by marking this post as the "Solution"! Let us know if you have any feedback here.
, 
, or 
. Or by marking this post as the "Solution"! Let us know if you have any feedback 