Skip to main content
Most problems in Mythos fall into a handful of patterns. This page lists each one with what you see and what to do. If a build failed, the first thing to know is that you were not charged — every generation ends in either a delivered result or a full refund, never a silent loss of credits.
Cost reminder: a new project costs 3 credits, an edit costs 2, a template remix costs 5. A build that fails is refunded in full automatically — re-prompting after a failure costs nothing extra. See Credits & pricing.

​
Common issues

No. Every generation ends in exactly one of two states: a delivered, verified result, or a clean message plus a guaranteed refund. If a build did not deliver, the credits go back to your balance automatically — you are never charged for a result you did not get.What to do: read the message, then re-prompt. A failure is usually transient, so sending the same prompt again often works. If it keeps failing, try making the prompt more specific or breaking a large request into smaller steps.
OutcomeWhat you seeYour credits
DeliveredA result card with a previewSpent (3 build / 2 edit / 5 remix)
RefundedA short, plain message that something went wrongRefunded in full — re-prompt free
If your prompt asked for a lot at once, a smaller, clearer prompt is more likely to deliver in one build. See Writing good prompts.
A blank or white preview usually means the live preview is still starting up, or the page hit an error while loading.What to do:
  1. Give it a few seconds — the preview spins up after a build finishes.
  2. Refresh the preview.
  3. Open the preview again from the result card.
  4. If it is still blank, send an edit describing what you expected to see (for example, “the page is blank — show the landing section”). The agent can rebuild the part that failed.
Apps Mythos builds are frontend-only by default. A form will look and behave correctly, but it has no database to save into until you connect one. Mythos uses bring-your-own Supabase: you connect your own Supabase project, and the agent wires the form up to it.What to do: connect a Supabase project in Services → Cloud, then ask the agent to save the form’s data. For example:
Connect this contact form to my Supabase project and store each submission in a "messages" table.
Until you connect a Supabase project, forms are simulated on the frontend only — they do not persist data. The connection is your own Supabase, not a Mythos-hosted database.
Publishing produces a production build of your site and serves it as static files. A change you made in the workspace after publishing does not appear on the live URL until you publish again — editing the project updates the preview, not the published site.What to do: make your edits, confirm them in the preview, then re-publish so the live URL picks up the new build.
A published site is public on the internet. Re-publishing replaces what visitors see — make sure the change is what you want live before you publish.
A new project costs 3 credits, an edit costs 2, and a template remix costs 5. When your balance is too low for the next action, the build will not start.What to do: buy more credits. Open Pricing from your dashboard or the credits menu and pick a pack:
PackCreditsPricePer credit
Pro (most popular)100$30$0.30
Ultra1,000$270$0.27
Both packs are paid once in USDT on the TRON network (TRC-20), and credits never expire. New accounts also start with 5 free credits. See Credits & pricing.
Unused credits can be refunded in USDT within 30 days of purchase — reach out on Telegram @mythos_support.
Plan mode is free — answering questions and reviewing a plan costs nothing, so you can shape a project without spending credits until the build runs. See Plan mode.

​
Still stuck?

If none of the above fixes it, reach support on any of three channels: email support@mythos.new, Telegram @mythos_support, or the in-app support form on the Help page. All three land in the same queue and we reply within one business day. When reporting a bug, include what happened, what you expected, and any project IDs or URLs. See Support policy for what is covered.