GitLab

GitLab is a platform for storing code, organizing technical work and reviewing changes before they ship. It is where many teams keep their projects, issues and merge requests.

This connector lets your AI work with GitLab through the official API: it can search projects, read files, create issues, prepare merge requests, create branches and push changes when you ask. The official README describes it as a server for the GitLab API enabling "project management, file operations, and more".

What you can ask

• "Find the website repository and explain which files seem to control the pricing page."
• "Create an issue to review the onboarding flow, with these steps and labels."
• "Prepare a branch and merge request with this README copy change."

What token you need

You need a GitLab Personal Access Token. Create it from your GitLab profile; the official README says to go to User Settings > Access Tokens and select the permissions you need.

1. Open GitLab's official guide for personal access tokens: https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html.
2. Create a new token for Terminal Sync, with a reasonable expiration date.
3. Choose scopes based on the job: read_api to inspect information, read_repository to read repos, write_repository if you want it to push changes and api if you need full API access.
4. Paste the token when the Lab asks for GITLAB_PERSONAL_ACCESS_TOKEN. Terminal Sync stores it encrypted in your Keychain.
5. If you use self-managed GitLab, change GITLAB_API_URL to your instance URL, for example https://gitlab.yourcompany.com/api/v4.

Start safely with the smallest set of scopes, then expand only when you need the AI to write changes.