Frequently asked questions

Sign in with the account that has access to the workspace. Use the account-creation flow offered by Mythos if you need a new account, then follow any invitation or access instructions. See Signing in and accounts.

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.

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.

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.

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.

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 charges consumed work within the accepted limit and returns unused credits. Read the message, check the balance, and adjust an unclear or oversized request before trying again. If the same failure repeats, use Troubleshooting.

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.

Yes, with an active Pro or Business plan and permission to edit the project. 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.

No. A visual form should not be treated as persistent storage unless the application has a real backend and the form writes to it. You can connect your Supabase organization and ask Mythos to add saved submissions. Test a submission and check that it remains after reloading. See Managed Supabase backend.

Yes. Anyone with the URL can open a published site. Review visible content and remove private information before you confirm Publish.

No. Edits update the workspace Preview. Publish again when you want the latest delivered version to replace what visitors see.

Builds and edits charge usage within your selected limit. Plan turns cost 1 credit and template remixes cost 5 credits. 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 charges consumed work and returns the unused reserve. See Credits and usage for the current amounts and plan requirements.

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.