Skip to main content
GitLab is an alternative to GitHub as your code host. Connect once at the account level; every Hideout project against a GitLab repo reuses that connection. gitlab.com is supported today. Self-hosted GitLab is on the roadmap — the connection routes through gitlab_base_url, so a single config change will enable it.
Where: Platform → Profile → Integrations tab. Click Connect GitLab.

​
What we ask for

The GitLab OAuth scope is api — read and write access to the resources you authorize. Hideout uses it to:
  • Read your codebase when an agent launches.
  • Push branches and open Merge Requests.
  • Read commit and branch state for the Agents page.

​
Per-user authorization

GitLab connections are per-user — the connection sees every group and project your account can access. The project picker in the New Project wizard lists what’s visible to you; pick a repo and a branch and Hideout uses that combination for clones and MRs.

​
Disconnecting

Profile → Integrations → GitLab → Disconnect clears the tokens and removes Hideout’s authorization. Projects you’ve created against GitLab repos lose their repo link; teammates’ connections to the same repo aren’t affected.

​
Troubleshooting

  • “GitLab connection expired” — your OAuth token was revoked or rotated. Reconnect from Profile → Integrations.
  • Agent unable to read codebase — check that the project’s connected repo is still accessible to the connecting user and that branch permissions allow Hideout to push.
  • Repo not in the picker — the OAuth token only sees what your GitLab account sees. If a teammate connected the repo originally and you can’t, check your GitLab group membership.