Skip to main content
The words Mythos uses, defined once. This is the page to check when a term is ambiguous or when an older name shows up somewhere — Mythos has been renamed and re-architected more than once, so this glossary also records what things used to be called and what was removed.
Mythos is pay-as-you-go. Some terms below cost credits (a Plan AI turn, a build, an edit, a template remix); each definition says so. New accounts start with 5 free credits. See Credits & pricing.

​
Core terms

​
Credit

The unit you spend on an AI action. An accepted Plan AI turn costs 1 credit, a new project 3, an edit 2, and a template remix 5. A Plan turn keeps its reservation only after a durable response is saved; a failed Plan turn or Build is refunded. New accounts start with 5 free credits. Credits are bought in packs and never expire. See Credits & pricing.

​
Build

Creating a new project from a prompt — Mythos scaffolds a full React 19 + Vite project, writes the components, and commits it to a private repository it manages for you. Costs 3 credits. Also the verb for what the agent does each time it generates code. (Connect your GitHub account and Mythos creates a new private repository you own with two-way sync on one selected active branch.)

​
Edit

A change applied to an existing project — Mythos modifies the code and lands a new commit. Costs 2 credits. Edits are how you iterate after the first build (“make the hero darker”, “add a pricing section”).

​
Build mode

The default way to generate: Mythos builds directly from your prompt, with no questions first. Contrast with Plan mode below. Toggle between them next to the send button in the composer.

​
Plan mode

A guided start. Before building, Mythos asks focused questions and saves a durable, editable plan draft for you to review and approve. Each accepted AI turn costs 1 credit after its response is saved; failed turns are refunded, local draft edits are free, and the Build after approval is charged separately. See Plan mode.
Build mode vs Plan mode. Build mode = straight from prompt. Plan mode = questions → editable plan draft → approval → Build. Both produce the same kind of project; Plan mode shapes its scope first.

​
Project

One app you are building — its code in a private repository Mythos manages, its chat history, and its connected backend (if any). Your projects live in your dashboard; opening one takes you into the workspace.

​
Workspace

The screen where you work on a single project: the chat (where you prompt Mythos), the live preview, and the built-in code editor (the workspace IDE). Distinct from the dashboard, which is the tray of all your projects.
Workspace IDE vs the Mythos-built site. The workspace IDE is Mythos’s editor where you read and edit your code. The site it builds is your app. The IDE requires a wider screen — on phones it shows a notice to switch to a larger device.

​
Publish

Shipping your project to a live, public URL. Mythos runs a production build and serves it from a *.r21.dev address; you can point a custom domain at it afterwards. Publishing is a deliberate step — your project is private until you publish it. See Publishing.
Publishing makes your site public on the internet. Anyone with the URL can see it. Review what you are shipping — Mythos scans for obvious secrets, but you are responsible for what goes live.

​
Artifact

A downloadable file Mythos generates for you on request — a PDF, CSV, XLSX spreadsheet, or chart — plus any files you upload in chat. Artifacts live in the project’s Files tab. They are separate from your app’s source code. See Files & artifacts.

​
Template remix

Forking a ready-made multi-page template into your own new project, which you then customize by prompting. Costs 5 credits. Start a remix from the template gallery.

​
BYO-Supabase / Cloud

Bring-your-own backend. Mythos builds the frontend; for a database, auth, and storage you connect your own Supabase project. Once connected, the Cloud console (under More → Cloud in the workspace) lets you manage that Supabase — its database, users, storage, and SQL — from inside Mythos, and the agent can wire your forms and data into it.
Your Supabase, not ours. Your data and credentials stay in your own Supabase account. Mythos stores your connection encrypted and the agent sees only the public URL and anon key. See Welcome to Mythos.

​
Rename history

Mythos has changed names and swapped major pieces. These older names still appear in old links, screenshots, and search results — here is what they map to now.
“Cloud” means two different things historically. The retired Mythos Cloud was a backend we hosted. Today’s Cloud console manages your own connected Supabase. Only the second one exists now.
No. Clerk was removed in 2026-05. You sign in with Google, GitHub, or a one-time email code — there is no Clerk account to create.
It was retired. Mythos is frontend-first; for a backend you connect your own Supabase project, which you then manage from the Cloud console in the workspace.
The old paste-a-key connector system was removed. In dashboard Connectors, the Supabase entry connects your backend account; More → Cloud then lets you choose one of its projects for the current app without copying project keys. The separate Ready connector catalog covers Notion, Linear, Resend, Airtable, Google Analytics, Custom MCP and Custom API; Stripe is Coming soon.