Blog / Product

GitHub Sync and Export: Your Mythex Code Is Yours

Everything you build on Mythex belongs to you. Sync a project to GitHub, download it as an archive, or import one back in. How each works, and the limits.

Mythex Team · 2026-09-29 · 3 min read

The code you build on Mythex is yours, and you can take it with you. On Pro, you can sync a project to a GitHub repository, download the whole thing as a .tar.gz archive, or import an archive back into a project. Secrets are left out of exports, so an archive is safe to move around.

What it does

Mythex gives you three ways to move code in and out of a project:

  • GitHub sync — link a repository and push or pull between it and your project.
  • Export — download the project as a .tar.gz archive from project settings.
  • Import — replace a project's files with the contents of a .tar.gz, .tgz or .zip.

If you haven't used GitHub before, what GitHub is covers the basics: it's where most developers keep code, track changes, and review each other's work.

Why it matters

An app builder that holds your code hostage is a risk. If you outgrow it, hire a developer, or just want a copy on your own machine, you should be able to walk away with everything.

Mythex's data ownership page puts it plainly: everything built in your project belongs to you. You can keep building in Mythex, export it, or sync it to GitHub. GitHub sync is also the natural hand-off point when an engineering team takes over — they get a normal repository with the full project in it.

How to use GitHub sync

  1. Connect GitHub from settings while you're logged in to Mythex. This uses GitHub's OAuth sign-in.
  2. Link a repository to the project.
  3. Push or pull from the project against that repository.

The GitHub connection is only for syncing repositories. It isn't a way to sign in to Mythex — you still sign in with email or Google.

A tip from the docs: make a clean checkpoint before doing any force-push style operations on your own remotes, so you have somewhere safe to return to.

How to export

  1. Open project settings → Export.
  2. Download the project as a .tar.gz archive.

Secrets and node_modules (installed packages, which can be rebuilt) are excluded. That makes the archive safe to share or to move between environments. You'll need to add your secrets again wherever you run it. If you plan to run the app somewhere else, how to export and self-host an AI-built app walks through the steps.

How to import

Import brings an archive into the current project. There isn't a separate "create a project from an archive" flow on the dashboard, so start a project first if you need an empty one.

  1. Open project settings → Export.
  2. Choose Import into this project.
  3. Pick a .tar.gz, .tgz or .zip file.

What happens:

  • The project's files are replaced by the archive's contents.
  • The project's existing secrets stay.
  • Any .env files in the archive are stripped. Re-add those values in Settings.

Import is useful for restoring a backup or bringing an existing codebase into an empty project.

What Mythex keeps hosting

Exporting gives you a copy; it doesn't move anything off Mythex. While a project exists, Mythex hosts:

  • The project files, in your private sandbox
  • The database and file storage, if you've turned them on
  • The published app, until you unpublish it or delete the project

Deleting a project or your account removes your apps from Mythex hosting. Export first if you want a local copy.

Secrets and Git

The API keys in your project's secrets are for your app when it runs. Don't commit them to Git. Exports already leave them out, and imports strip .env files, so the defaults help — but if you add files to your repository by hand, keep keys out. What environment variables and secrets are explains why.

Limits

  • Export and GitHub sync are Pro features. On Free you can view code read-only and use Preview and the terminal; upgrade to download or sync.
  • Import replaces files. It doesn't merge. Export first if you might want the current version back.
  • Exports exclude secrets and node_modules. Plan to re-add keys and reinstall packages elsewhere.

Read more

  • GitHub, export, and import
  • Data ownership

Keep reading

  • A Landing Page for Every Kind of Business — Search for a booking system for a dental clinic or a website for a bakery and land on a Mythex page written for that business, with a prompt ready to build it.
  • A Private Workspace and a Live Preview for Every Project — Every Mythex project runs in its own private cloud workspace with a live preview beside the chat. How it works, how to use it, and what to expect.
  • Auto-Reload: Keep Your Published App Running When Credits Run Low — Auto-reload buys Mythex credits when your balance runs low, so a long build or a busy published app does not stop at zero. How to set it up, and its limits.
  • Build Mythex Apps from Claude, Cursor or Codex — Mythex runs a remote MCP server: connect Claude, Cursor or Codex, and they code in your Mythex cloud sandbox with a live preview, database and publishing.
  • Checkpoints: Undo Any Change the Agent Makes — After every successful turn, Mythex saves a checkpoint of your project. Revert to any of them in two clicks, or edit an earlier message and try again.
  • Connect Gmail, Google Sheets and Slack to Your App Builder — Mythex Connectors link Gmail, Google Sheets, Slack, Notion and more to the chat agent, with no API keys in your code. How it works, setup, and limits.

Start building free · Templates · Docs