This guide assumes you are an Owner of the GitLab group (or a Maintainer of the projects) you want CodeAnt AI to review merge requests for. Works the same for GitLab Cloud and self-hosted GitLab.
Overview
CodeAnt AI reviews merge requests on GitLab by calling the GitLab API on your behalf and listening for repository events through webhooks. The fastest path is two steps:- Create a GitLab access token CodeAnt AI can use.
- Paste the token into CodeAnt AI — webhooks install automatically on the projects you select.
Step 1: Create the access token
The same token guide applies for GitLab Cloud and self-hosted GitLab.Create your GitLab access token
Choose a token type, generate it in GitLab, and copy the value before closing the page.
Step 2: Paste the token into CodeAnt AI
This is where webhooks get installed for you — CodeAnt AI uses the token to detect which of your projects are missing webhooks and creates them via the GitLab API.- Sign in to app.codeant.ai with GitLab.
- Open Settings → Configure Token.
- Paste the access token and click Save & Configure Webhooks.
- On the Configure Repository Webhooks screen, CodeAnt AI lists every project missing a webhook. Use the search field and Select All to pick the projects you want reviewed, then click Create Webhooks (N).
Troubleshooting
The sidebar shows a 'GitLab token expired' banner
The sidebar shows a 'GitLab token expired' banner
Merge requests aren't getting reviewed
Merge requests aren't getting reviewed
- Open Settings → Configure Token in CodeAnt AI and confirm the project appears in the list with a webhook installed. If it’s still in the “missing webhooks” list, select it and click Create Webhooks.
- If the auto-install failed for a specific project, the token user (or service account) likely doesn’t have Maintainer access on that project. Fix the permission and reconfigure the token to retry.
- In GitLab, open Settings → Webhooks on the project and use Test → Merge request events to confirm CodeAnt AI is reachable. A 2xx response means the webhook is wired up correctly.
Reviews are attributed to the wrong user
Reviews are attributed to the wrong user
Reviews are posted as the user who owns the access token. Switch to a service-account personal access token or a group access token if you’d rather not use your own account — see the access token guide.
I'm on Ultimate and want a single group-level webhook instead of per-project ones
I'm on Ultimate and want a single group-level webhook instead of per-project ones
Group-level webhooks aren’t created automatically. Follow Manual Webhook Setup to add them yourself.