> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.mythos.new/introduction/faq/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.mythos.new/_mcp/server.

# Frequently asked questions

> Short answers about accounts, 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

#### How do I access my workspace?

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](/introduction/sign-in).

#### 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](/features/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](/features/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 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](/reference/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, 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.

## Data and publishing

#### Will a form save submissions automatically?

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](/integrations/supabase).

#### 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?

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](/introduction/credits-and-usage) for the current amounts and
plan requirements.

#### How do I get help?

Start with [Troubleshooting](/reference/troubleshooting). If the issue
remains, use a confirmed channel listed in [Support policy](/reference/support-policy) and include the project, what you
expected, and what happened.

> Learn how to turn an idea into a working app, improve it in Mythos, and publish it when it is ready.