Troubleshooting

When a run fails, the chat shows the error and the canvas keeps your previous draft, so nothing is lost. Most problems are with the key, the model or the account.

Key problems

The provider didn't accept the key (401)

The key is wrong, expired or revoked. Copy the secret key itself, not its ID. Anthropic key IDs start with apikey_01 and aren't the key. Create a new key if you can't find the secret; it's only shown once.

The key was accepted but the request was refused (403)

Your key may not have access to the model you picked. Try another model, or check the model's access in your provider account.

The key dialog warns about what I pasted

Read the message under the field. It catches keys from a different provider, Admin keys, subscription tokens, key IDs, and stray spaces or line breaks. Fix what it says, then save.

Quota and credit

"You've used today's quota"

The model's daily limit is used up. Vibr already tried its backup. Pick another model now, or turn on billing for higher limits. Gemini's free daily limits reset at midnight Pacific time.

"Limiting how many requests per minute"

Wait for the time the message gives, usually under a minute, then try again. Or pick another model.

"This key's account is out of credit"

Add credit or billing in your provider account. Vibr doesn't switch to the backup for this, since the backup uses the same account.

Model problems

The provider is overloaded (503)

The provider is busy. Vibr retries and tries the backup model first, so if you see this, wait a minute or pick another model.

The model isn't recognized (404)

The provider no longer offers that model, or your key can't see it. Pick another model.

It hit its output limit before the code was finished

The screen was too big for one answer. Ask for a smaller screen, or build it in steps, one section per message.

The model declined to answer

Rephrase the request.

Draft problems

The preview didn't render

Check failed and Repair couldn't fix it. Send a follow-up describing what you want, or go back to the previous version with Undo and try again.

"Isn't exported by" a package

The model used a component the design system doesn't have. Vibr lists the closest real names in the error. Repair usually fixes this; if not, ask for the closest component by name.

"Couldn't find it on npm"

The custom package name or version is wrong. Check the spelling and the version on npmjs.com.

Timed out

A step took longer than 45 seconds to render, often because a package was slow to load. Try again.

Library problems

"This browser's storage is full or turned off"

Delete prototypes, images or videos you no longer need, or export and remove them. Private browsing windows may not allow storage at all.

"That file isn't a Vibr library export"

Import only .json files exported from Vibr. To bring in images, videos, fonts or tokens, use the Images, Videos, Type ramp, Icons or Themes tab.