LaunchWithCursor

Knowledgebase

MissionWorkflowInstallUpdatesPromptsGitEnv varsDeployHandoffTesting
Knowledgebase6 min read

Transfer ownership

Fix GitHub access when a repo moved, a client handoff, or org OAuth blocks deploy.

Projects sometimes change hands — you bought a codebase from another founder, a client added you as an editor, or the GitHub repo moved to a new organization. LaunchWithCursor and GitHub each have their own access rules; fixing both is what unblocks deploy again.

This guide is for repository access after a handoff, not for transferring a LaunchWithCursor project between workspaces (use Platform → Project transfer for that).

Need Git basics first? See Git & GitHub. Ready to deploy again? See Deploy & hosting.

Repository URL changed

If the code moved to a new GitHub repository (different URL):

  1. Open Deploy → Overview for the project.
  2. Update the repository URL to the new location.
  3. Confirm your GitHub account still has read access to that repo.
  4. Deploy again.

Use HTTPS (https://github.com/org/repo) or SSH ([email protected]:org/repo) URLs when linking the repository.

Contributor cannot deploy (access denied)

LaunchWithCursor deploys using your personal GitHub account linked under Settings → Connections — not the workspace owner's account.

Being an owner, admin, or editor inside LaunchWithCursor does not bypass GitHub. GitHub must allow your user to clone the repo.

Ask a repo admin to:

  • Add your GitHub username as a collaborator (read access is enough), or
  • Confirm you are a member of the GitHub organization that owns the repo.

Then reconnect GitHub on LaunchWithCursor and try deploy again.

Organization repos after a project handoff

This is common when a project moves to another workspace or the repo lives under a client's GitHub organization — for example after you transfer a project and they add you back as an editor.

Symptoms

  • Deploy or Sync from repo returns a forbidden / GitHub access error.
  • Nothing new appears under Deployments — the build never queued because GitHub blocked the clone.

Fix it

  1. Link GitHub on LaunchWithCursor (Settings → Connections) with the same GitHub user you use on the repository.
  2. Confirm you are a collaborator on the repo (read access is enough).
  3. If the repo is under a GitHub organization, you need both of these (linking a personal account alone is not enough):
    • Org admin: open Organization → Settings → Third-party access and approve LaunchWithCursor. On Deploy, LaunchWithCursor shows a direct link to your org's OAuth settings and a Copy instructions for admin message you can paste to your client's GitHub admin.
    • You (the deployer): open the LaunchWithCursor authorization link from Deploy or Settings → Connections, click Grant next to the org, then Reconnect GitHub on LaunchWithCursor.
  4. If the repository URL changed during handoff, update it on Deploy → Overview before deploying again.

Who does what

RoleAction
GitHub org adminApprove LaunchWithCursor OAuth for the org
Repo adminAdd your GitHub user as a collaborator
You (editor on LaunchWithCursor)Connect GitHub, then deploy again

Until GitHub allows your account to read the repo, deploy will not start — the dashboard cannot show a build that never queued.

When to ask your AI coding assistant

Paste the exact error from Deploy → Deployments (use Copy log) into Ask mode in your editor. Ask it to explain whether the problem is GitHub access, a wrong repo URL, or something in the build — before switching to Agent mode to fix code.

Related guides