Chat & generation

Fix AI chat, build credits, and code generation issues in OpenV2.

The Chat builder drives most changes in OpenV2. These are the most common issues when chatting or waiting for the AI to finish.

Chat not responding or request failed

  1. Check your internet connection and refresh the page.
  2. Confirm you are signed in — session expiry can block new requests.
  3. If you see a rate-limit or server error, wait a minute and try again with a shorter message.
  4. Avoid sending a new message while a generation is still in progress — let the current run finish or cancel it first.

Out of build credits

When credits are exhausted, chat generation stops until your balance refreshes or you add more.

  • See your balance in Settings or the upgrade modal
  • Plans & credits — how credits reset and what consumes them
  • Usage & top-ups — one-time credit packs and tips to save credits

Free tier credits refresh daily; paid plans reset monthly from your subscription date.

Generation stopped mid-way or looks incomplete

  • Scroll the chat — multi-step runs may show a plan or tool steps before file changes appear.
  • If files were partially edited, check Version history and restore if needed.
  • Send a follow-up: "Continue where you left off" or describe what is still missing.

The AI misunderstood my request

  • Be specific: screen name, user flow, colors, and what should not change.
  • Attach a design reference or sketch when layout matters.
  • Use Plan mode for large features so you can approve the approach before code is written.
  • Restore a good version from history, then retry with a clearer prompt.

Too many files changed at once

  • Break the request into smaller steps (e.g. "Only update the home screen header").
  • Edit one area in the Code editor if you know the exact file.
  • Enable or load relevant Skills & knowledge for specialized tasks.

Preview broke after a chat edit

  1. Open Preview logs and copy the error.
  2. Ask: "Fix the preview error without changing unrelated files."
  3. Or roll back via Version history.