A clear path forward

How do personal Git connections differ from shared workspace access?

Your personal Git connection lets Agent work with your code during a chat. A workspace connection gives shared environment builds their own approved access to repositories.

VerifiedRH-0118v1

The two are separate because a background build cannot rely on your active chat session. A personal connection that can read code does not prove that a shared build can fetch the same repo.

Start by connecting your personal GitHub or GitLab account so Agent can work on repositories you can access. If your team also needs shared environment builds, a workspace administrator can configure shared repository access separately.

You do not need to complete both setups just to make your first contribution.

  • Connect your personal account
  1. Switch to the Replit workspace where you want to work.
  2. Open Repos and find GitHub or GitLab.
  3. Select “Connect.” If the card shows “Manage,” open it and select “Connect” in the personal connection section: “GitHub” for GitHub, or “Personal account” for GitLab.
  4. Sign in to the intended GitHub or GitLab account and complete the authorization flow.
  5. Return to your chat, share the full repository URL, and ask Agent to get it running.

Your account needs permission to read the repository. Pushing changes or opening a pull or merge request also requires the appropriate permissions for your team’s contribution workflow.

  • Set up shared GitHub access

A Replit workspace administrator configures this connection. A GitHub organization owner or administrator may also need to install or approve the App. These can be different people.

  1. In the intended workspace, open “Repos” → “GitHub” → “Manage.”
  2. Find “GitHub App.” If “Connect” is shown, complete the sign-in flow, then select “Configure.”
  3. Select “Add GitHub organization” and complete GitHub’s installation or approval flow. Choose the organization and repositories your team needs.
  4. Return to Replit and select “Refresh” if the organization is not listed.
  5. Select “Enable” beside the organization.
  6. Confirm that it shows “Enabled” and that the intended repositories are available.

Installing the App on GitHub does not automatically enable its access in your Replit workspace. Complete both sides of the setup.

  • Set up shared GitLab access

A Replit workspace administrator configures this connection using a GitLab account with the required group and project permissions.

  1. In the intended workspace, open “Repos” → “GitLab” → “Manage.”
  2. Under “Workspace account,” select “Connect” or “Configure.” Sign in to GitLab if prompted.
  3. Select “Configure” beside the group you want to connect.
  4. Select the projects to share, then choose “Connect group.”
  5. Confirm that the group shows “Connected.” To change the selected projects later, choose “Edit,” update the selection, and select “Save changes.”

GitLab uses group and project access, not a GitHub-style App installation.

If a repository is missing, check the account you signed in with, the selected Replit workspace, and the repositories or projects authorized for that connection. For GitHub shared access, check the App’s repository selection on GitHub as well.

Personal and workspace access are separate. A successful personal connection does not prove that a shared environment build can fetch the same repository.

Was this page helpful?

Still stuck? Try troubleshooting with Agent.

Copy this prompt and paste it into Agent. For a project issue, open the project where it happens first. Add what happened and anything you've already tried. Don't include passwords, API keys, database connection strings or payment-card details.

Copying does not open Agent or send a support request. Agent availability and usage depend on your account.

Can't open your project, or need another kind of help? Get help.

Share or save this answer

Send a link

Point someone to this answer.

Save the answer

Paste the answer into your notes.

Last updated