
Features
- Open merge requests with code changes
- Respond to MR feedback and iterate
- Auto-fix failed CI/CD pipelines
- Scan for TODOs, security issues, and tech debt
Installation
Tembo supports a shared GitLab service account or a personal account connected through OAuth. We recommend a service account so the integration does not depend on an individual team member.Connect a service account
You must be a Tembo organization admin. On GitLab.com, you must also be an Owner of the top-level group and may need to verify your identity. For GitLab Self-Managed or Dedicated, you must be an instance administrator or an Owner who is allowed to create service accounts.1
Create a GitLab service account
In GitLab, open your top-level group and go to Settings → Service accounts. Select Add service account, name the account, and select Create service account.See GitLab’s service account instructions for GitLab.com and self-managed prerequisites.
2
Grant repository access
Add the service account as a member of the top-level group or each project that Tembo should access. Assign the Maintainer role so Tembo can create project webhooks as well as branches and merge requests. GitLab requires the Maintainer or Owner role to create project webhooks.
3
Create an access token
On Settings → Service accounts, open the service account’s menu and select Manage access tokens → Add new token. Enter a name and expiration date, select only the
api scope, and select Create personal access token. Copy the generated token.GitLab documents token creation, expiration limits, rotation, and revocation under Create a personal access token for a service account.4
Connect Tembo
In Tembo, go to Integrations and select Install next to GitLab. Paste the token into Service account access token, then select Connect with access token.
5
Activate repositories
Select which repositories Tembo should work with under Active Repositories.
Tembo rejects tokens owned by regular personal user accounts. When the service account token expires, is rotated, or is revoked, reconnect the integration with the new token.
Connect with OAuth
Go to Integrations, select Install next to GitLab, and select Continue with OAuth. Authorize access, then select which repositories Tembo should work with under Active Repositories.Usage
MR comments
Comment@tembo on any merge request to request changes. Works in the main thread or as inline review comments.
Agents
See Agents for available GitLab event triggers.Failed pipelines
Tembo can detect CI/CD pipeline failures and open fix MRs automatically. Set up an agent with a pipeline failure trigger.Advanced
Repositories not appearing
Repositories not appearing
Wait 2-5 minutes for initial sync. Click the sync button on the GitLab integration card to refresh. Check that you granted access during installation.
@tembo not responding
@tembo not responding
Make sure you’re using
@tembo (lowercase) and that the repository is activated in Integrations.MRs not being created
MRs not being created
Check that the repository is activated and there isn’t already an open MR for the same issue.