Help
Frequently asked questions
Short answers about private access, building, editing, connected data, publishing, credits, and support.
These answers cover the decisions most people meet first. Follow the linked guide when you need the full workflow or an edge case.
Access and accounts
Can anyone create a Mythos account?
No. Mythos is currently in private, owner-only access, and public registration is closed. An existing authorized account can sign in normally. See Signing in and accounts.
How do I sign in?
Use Google, GitHub, or a six-digit one-time code sent to the email linked to your authorized account. Mythos does not use a password sign-in flow.
Building and editing
Do I need to know how to code?
No. Describe the result in the conversation and refine it with follow-up requests. The workspace editor is available when you want to inspect or change a file directly, but it is optional.
Should I choose Build or Plan?
Choose Build when the request is clear and you want a result immediately. Choose Plan when important requirements are still open: Mythos asks focused questions, prepares an editable draft, and waits for approval before starting the Build. See Plan mode.
How do I change a result?
Open the project and send a focused edit that names the section and desired change. You do not need to repeat the whole original prompt. See Building and editing.
What happens if a Build fails?
A failed run does not replace the current project version. A platform failure before delivery normally returns the reserved credits, while choosing Stop after AI work has begun keeps the fixed charge. Read the message, check the balance, and adjust an unclear or oversized request before trying again. If the same failure repeats, use Troubleshooting.
Can I undo a change?
Yes. Open History, preview an earlier version, and choose Revert if you want it back. A revert creates a new current version; it does not erase the versions that came after it.
Can I edit a file myself?
Yes, on a desktop browser. Open Code, select a text file, make the change, and choose Save or press Ctrl+S (Cmd+S on macOS). Direct file edits do not run the AI builder.
Data and publishing
Will a form save submissions automatically?
No. A visual form should not be treated as persistent storage unless the application already has a real backend. New backend connections are not currently available in the workspace; the former Supabase Cloud flow is retired. See Supabase connection status.
Is a published site public?
Yes. Anyone with the URL can open a published site. Review visible content and remove private information before you confirm Publish.
Do later edits update the live site automatically?
No. Edits update the workspace Preview. Publish again when you want the latest delivered version to replace what visitors see.
Credits and help
How do credits work?
AI actions use fixed credit prices. Direct file edits, history inspection, revert, and publishing do not start an AI run. Platform failures before delivery normally return reserved credits, while Stop after AI work begins keeps the fixed charge. See Credits and usage for the current amounts and owner-only availability.
How do I get help?
Start with Troubleshooting. If the issue remains, use a confirmed channel listed in Support policy and include the project, what you expected, and what happened.