GitHub | Cofounder Docs

GitHub

During onboarding, Cofounder creates two managed GitHub repositories:

These repositories are private and auto-initialized during provisioning.

Role

GitHub is where the code lives.

What Cofounder Sets Up

After the repositories are created, Cofounder also seeds:

How GitHub Connects To The Rest Of The Stack

The managed GitHub repositories are what the managed Vercel projects get linked to during onboarding.

They are also the repositories the engineering agents work against when they open branches, make changes, and put up pull requests.

Repository Access And Invites

If you cannot open the managed repositories in GitHub, make sure your Cofounder account is signed in with GitHub or linked to the GitHub account that should receive access.

Agents work through Cofounder's connected repository context. If GitHub is not connected, do not use an agent as a workaround by asking it to clone a private repo manually. Connect GitHub through the in-app sign-in or account-linking flow, then use the supported repository access flow instead.

Organization admins can invite a GitHub user to the managed app and marketing repositories from Settings > Advanced under Get access to managed repos. Enter the user's GitHub username and Cofounder will send repository collaborator invites for the managed repositories. The user should then accept the GitHub invites from GitHub.

Import Your Own Repo

Some workspaces also let you replace the managed app repo or marketing repo with a repo you already own.

That flow lives in Settings > Advanced.

It covers:

For app repos, it can also keep managed Supabase env wiring, migrations, and the prod branch setup aligned.

Next Steps