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

# Connect GitHub

> Create a private GitHub repository for your Mythos project and keep one selected branch in sync.

Connect GitHub when you want your Mythos project in a private repository that you control. You can
clone the code, work with your team, use your own development tools, or deploy it somewhere else.

Mythos creates a **new private repository** in the GitHub account or organization you choose. It then
keeps one selected branch synchronized with the project in Mythos.

> **Note**
>
> Connecting GitHub and using two-way sync require an active **Pro or Business**
> subscription in the workspace and project-owner access. The project also needs
> saved source from a completed Build or template remix. See the [current plans and pricing](https://mythos.new/pricing).
>
> If you only need a copy of the files, **Download codebase** in the Git view works
> without a GitHub connection. ZIP downloads also require an active Pro or Business
> subscription; having credits alone does not unlock either feature.

## Connect your project

#### Open Git

Open the project workspace and choose **More → Settings → Git**. Choose **Connect GitHub**.

#### Approve GitHub access

Sign in to GitHub and choose the account or organization where Mythos may
create the repository. Only approve an owner you intend to use for this
project.

#### Create the private repository

Choose the owner and repository name shown in Mythos, then select
**Connect**. If that name is already used, enter another name and try again.

#### Confirm the active branch

Mythos shows the connected repository, its current branch, and the sync
status. You can create a new branch from the current project or switch which
branch is active.

Connecting GitHub does not spend credits. Builds and edits continue to use the prices shown on
[Credits & pricing](/introduction/credits-and-usage).

## How synchronization works

* Changes you complete in Mythos are sent to the selected GitHub branch.
* Compatible changes pushed to that branch from GitHub can return to Mythos.
* Only one branch is active in Mythos at a time. Work on other branches stays in GitHub until you
  switch the active branch.
* Mythos shows when the repository is connected, synchronizing, or needs attention.

If both sides changed in a way Mythos cannot combine safely, it shows a conflict instead of
overwriting either version. Review the active branch before deciding which work to continue from.

## Work outside Mythos

The Git view includes the repository link and clone commands for HTTPS, SSH, and GitHub CLI. Use the
method already configured on your computer. You can then open the project in your preferred editor,
invite collaborators through GitHub, or connect your own hosting workflow.

You can also choose **Download codebase** for a local copy without a GitHub connection.

## Disconnect GitHub

Disconnecting stops synchronization for the Mythos project. It does not delete the private repository
from your GitHub account. To connect again, return to the Git setup and review the new repository it will create. Use
**Reconnect GitHub** on an existing connection when the goal is to restore lost authorization.

> **Warning**
>
> Do not add private keys or production secrets to browser code or prompts.
> Review changes made outside Mythos before pushing them to the active branch.

## Troubleshooting

#### Recent changes are missing

Confirm that you are viewing the selected active branch, then choose
**Refresh sync**. If the Git view says the connection needs attention, use
**Retry sync** or reconnect GitHub.

#### GitHub access expired

Select **Reconnect GitHub** and approve the account or organization again.
Mythos keeps the existing repository; reconnecting restores access to it.

#### The project shows a conflict

Mythos and GitHub both changed since their last shared version. Review the
active branch and the current Mythos project, then select **Refresh sync** to check the status.
Mythos does not resolve the conflict by overwriting it automatically. If it remains, ask the
project owner to review both sets of changes, or contact support with the project and branch.
Do not disconnect merely to hide the conflict.

## Related

* [Connect your tools](/integrations/introduction) — see the available connection types.
* [Managed Supabase backend](/integrations/supabase) — add saved data and application accounts.
* [Version history](/features/version-history) — review or restore an earlier Mythos version.

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