Glossary
Short definitions for terms you may see in the product or these guides.
Account
Your identity for signing in to Mythos. The account can belong to a workspace and have access to projects. Application accounts created in an app you build are separate from your Mythos account. See Signing in.
Workspace
The shared space that groups projects, members, billing, credits, and team settings. Workspace owners and admins manage its shared rules. See People and permissions.
Project
One app you are creating in Mythos, with its code, conversation, preview, generated files, settings, and version history. A project belongs to a workspace.
Project workspace
The screen where you work on a project. It brings together chat, Preview, Code, Files, and project tools. See Dashboard and workspace.
Build
A request that creates or changes an app, uses a connected tool, or produces a deliverable. Describe the outcome you want, then review the result. A request that only produces a file does not need to change the app’s code. See Build with Mythos.
Plan mode
A conversation for investigating a question or shaping work before building. Mythos can prepare an editable plan while leaving project code unchanged. Approve the plan when you are ready to build. See Plan mode.
Knowledge
Saved instructions and context for future Builds. Workspace knowledge applies across projects; project knowledge adds the details of one app. See Knowledge.
Skill
A named set of instructions for a repeatable task. Invoke a custom workspace skill with its exact
/skill-name in a Build prompt. Built-in skills provide Mythos’s own task guidance.
See Skills.
Room
A project’s conversation space for people collaborating on the app. It is separate from the chat where you ask Mythos to build. See People and permissions.
Preview
The working version of the app inside Mythos. Use it to check a delivered change before publishing.
Version
A saved point in the project’s code history. You can inspect an earlier version and revert to it without removing later history. A code revert does not roll back database records or actions already completed in an external service. See Version history.
Generated file
A downloadable output, such as a report, spreadsheet, chart, or image, held in the project’s Files area. It is separate from the website’s source files and from prompt attachments. See Generated files.
Publish
Make the reviewed version available at a public web address. Later changes stay in Preview until you publish an update. Publishing does not invite visitors to edit the project. See Publish your site.
Template
A ready-made project you can preview and remix as your own starting point. Your copy can be edited independently. See Templates.
Connector and connection
A connector is the available integration with a service. A connection is the account or credential you have set up for that service. A project link controls which project may use a shared connection. Connecting a tool for Build does not automatically add its behavior to your published app. See Connect your tools.
Managed Supabase backend
A backend in your own Supabase organization for an app’s database, accounts, storage, and server functions. Mythos can create and manage a dedicated backend for the project after you connect the organization. The project’s Cloud view provides backend controls. See Managed Supabase.
Row-level security
Database rules that decide which records a user may read or change. For example, a customer may read their own reservations but not another customer’s reservations. See Row-level security.
GitHub
An optional connection for keeping one selected project branch synchronized with a private repository in your GitHub account or organization. See Connect GitHub.