Clearer AI Credit Messages and Fewer Continue Prompts

Quasar now tells you whether you hit your organization's monthly AI allowance or a platform-level provider limit — and handles larger multi-page builds in one turn before asking you to Continue.

Updated 18d ago

In short

When AI chat hits a limit, the error now distinguishes your org's monthly credits from a temporary platform provider outage. Multi-step builds also run further in a single turn before pausing for Continue.

What we shipped

Two quality-of-life fixes landed for Quasar in the site editor:

Credit errors point to the right fix

Previously, some limit messages blurred together — especially when the upstream AI provider ran out of platform credits versus when your organization had used its monthly AI allowance. Now the chat panel shows distinct guidance:

Organization credits exhausted — upgrade your plan, add a top-up, or wait for the billing period to reset.
Platform provider unavailable — a temporary upstream outage; retry shortly rather than changing your org billing.

The distinction matters: one is under your control in Billing → Usage, the other is a platform-wide provider issue that usually clears on its own.

Fewer forced Continue steps on big builds

Quasar works in steps — each model invocation plus tool calls (create page, update metadata, reorder folder, and so on). Very large requests used to hit the per-turn step cap quickly, which meant pressing Continue repeatedly on a single batch job. The step cap is now high enough to cover typical multi-page builds in one turn. You may still see a Continue prompt on unusually large jobs — that is intentional, so a runaway tool loop cannot burn through credits unchecked.

Why it matters

Misattributed error messages send teams down the wrong path: upgrading a plan when the provider is temporarily down, or waiting when the real fix is a top-up. Clear copy saves support time and keeps editing momentum. For the full list of chat limits and recovery steps, see Chat and suggestions in platform docs.

Recommended workflow

Check Billing → Usage when you see an org-credit message — confirm whether you need a top-up or plan change.
Retry after a few minutes when the message mentions a temporary provider outage.
Press Continue when a large build pauses at the step limit, or split the request into smaller chunks ("create three pages" instead of "create twelve pages").
Start a new chat if context feels confused after many turns — see AI overview.

What is next

We continue tuning Quasar's step limits and error copy as new models and tool patterns land. If a limit message still does not match what you see in Billing, contact support with the exact wording from the chat panel.

Plain-Voice Quasar Chat Errors

MDX Placeholder Tags Render as Text

What we shipped

Two quality-of-life fixes landed for Quasar in the site editor:

Credit errors point to the right fix

Previously, some limit messages blurred together — especially when the upstream AI provider ran out of platform credits versus when your organization had used its monthly AI allowance.

Now the chat panel shows distinct guidance:

Organization credits exhausted — upgrade your plan, add a top-up, or wait for the billing period to reset.

Platform provider unavailable — a temporary upstream outage; retry shortly rather than changing your org billing.

The distinction matters: one is under your control in Billing → Usage, the other is a platform-wide provider issue that usually clears on its own.

Fewer forced Continue steps on big builds

The step cap is now high enough to cover typical multi-page builds in one turn. You may still see a Continue prompt on unusually large jobs — that is intentional, so a runaway tool loop cannot burn through credits unchecked.

Why it matters

For the full list of chat limits and recovery steps, see Chat and suggestions in platform docs.

Recommended workflow

Check Billing → Usage when you see an org-credit message — confirm whether you need a top-up or plan change.

Retry after a few minutes when the message mentions a temporary provider outage.

Press Continue when a large build pauses at the step limit, or split the request into smaller chunks ("create three pages" instead of "create twelve pages").

Start a new chat if context feels confused after many turns — see AI overview.