Skip to main content

​
Introduction

In this page we’ll configure the native Gitlab integration and learn how to:
  1. Get Gitlab to push events to Cosmos via webhooks
  2. Configure a Cosmos environment that git clones/fetches from Gitlab repo(s)
  3. Get Cosmos to automatically post onto a MR when the MR is created
  4. Deploy the MR author and MR reviewer experts via the Cosmos Advisor
For 4, below is the flow that will be followed by the Cosmos MR reviewer expert:

​
Prerequisites

To configure the one-time connectivity between Cosmos and Gitlab:
  • you must be a Augment admin
  • you must have Gitlab permissions to create a Gitlab service account and its access token with the api scope (required) and enable one of those four options:
    • (1) give that service account the Maintainer role on a group that would have access to the repos in scope OR
    • (2) give that service account a custom role with at least the Developer role and the admin_web_hook permission on a group that would have access to the repos in scope OR
    • (3) give that service account the Maintainer role on each of the repos in scope OR
    • (4) give that service account a custom role with at least the Developer role and the admin_web_hook permission on each of the repos in scope

​
Step 1 - Configure the native Gitlab integration

As a Augment admin, go to cosmos.augmentcode.com > Settings > Connectors > Browse Connectors > Gitlab Cloud > click on it:
Image
You’ll be redirected to this view:
Image
Let’s switch to Gitlab to create that group service account:
  • Navigate to your Gitlab group, then Settings > Service Accounts in the left sidebar
  • Click on Add service account
    • Name: Cosmos
    • Username: ex: augment-code-cosmos
  • Next to your service account > click on the 3 dots > Manage access tokens
  • Add new token
    • Name: Cosmos01
    • Expiration date - set the maximum
    • Select api scope
    • Click on Generate token
  • Copy the access token, we’ll need it shortly
Now you’ll make this service account a member of the projects/repos you want to surface in Cosmos. 3 options:
  • (1) give that service account the Maintainer role on a group that would have access to the repos in scope OR
  • (2) give that service account a custom role with at least the Developer role and the admin_web_hook permission on a group that would have access to the repos in scope OR
  • (3) give that service account the Maintainer role on each of the repos in scope OR
  • (4) give that service account a custom role with at least the Developer role and the admin_web_hook permission on each of the repos in scope
Let’s assume you’re going with (3) and make the service account a maintainer on given projects/repos:
  • Go to your project > left sidebar > Manage > Members > Invite members > select your service account > role ‘Maintainer’ > select your project (or all projects in the group) > Invite
Screenshot 2026 09 10 At 2 15 48 PM You should see this: Screenshot 2026 09 10 At 2 16 41 PM Now go back to Cosmos.
  • Paste the group service account’s access token into Cosmos and click on ‘Connect bot’:
Image
Cosmos will automatically:
  • Discover the repos
  • Register webhooks to react to events across those repos (if you added the service account as maintainer at the group level, Cosmos will automatically configure a centralized webhook at the group level to receive events from all the repos under that group. If instead you added the service account as maintainer per repo, Cosmos will automatically configure a webhook for each corresponding repo)
You should see this:
Image
If you don’t see your repos, double check the scopes of your service account and that it’s added as a member of your projects with the proper role.

​
Step 2 - Create a cloud environment

Let’s create a cloud environment with those Gitlab repos:
  • Configure your environment
    • Name: ex: ecomm-stack
    • Image: ex: keep the Cosmos default base image
    • Repositories: select your Gitlab repos
    • Refresh: toggle on
    • Spaces: keep the default space
    • Click on Create Environment
Image
Cosmos will create the cloud environment, git clone your repos and keep them up to date
  • Click on Done
You’ll see your new environment in your “Mine” tab:
Image
Now let’s do a quick test and create a session with that env:
  • Click on ‘Back to app’ top left to get back to https://cosmos.augmentcode.com > New session > bottom left of the prompt select your env, then click on Integrations and verify that Gitlab is selected, then send this prompt “What’s this repo about?”
That’ll start a session. Notice on the right sidebar Expert = Not set, Integrations include Gitlab, your selected env:
Your Gitlab integration and your cloud env are ready. It’s time to create your first Cosmos expert.

​
Step 3 - Create a MR deep reviewer expert

Cosmos has a large knowledge base and greatly assists with creating new experts. A common expert you’d create for your Gitlab repos is the “MR reviewer”, whose job will be to auto react to MRs being created and auto review them. Whenever you need to create new experts go ask the Cosmos Advisor:
  • Go to Cosmos (https://cosmos.augmentcode.com) > New session > select the ‘Cosmos Advisor’ expert, make sure the Gitlab integration is selected and prompt with “Create a MR author, a MR risk analyzer, a MR deep reviewer. The MR review should start whenever a MR gets created. Those experts should reuse the ecomm-stack env of this session”
The Cosmos Advisor may ask you to clarify what experts to deploy, it may recommend to include other experts (ex: helper experts), and if an integration is missing it’ll guide you to add it. Ultimately you should see this at the end of your session:
Go check where your experts are created:
Image
Cosmos Advisor configured some experts to react to Gitlab events, you can see those configured in cosmos.augmentcode.com > Settings > Automations:
Image
If you expand the Deep Code Reviewer (Gitlab Cloud) you’ll see its triggers:
Image

​
Step 4 - Create a new MR and observe your experts at work

  • Go to Cosmos (https://cosmos.augmentcode.com) > New session, implement a simple change ex: prompt with “add a hello world banner on top of the web app, then create a MR in ready to review state”
Then open your MR, you’ll see the MR Risk analyzer expert commenting on the MR, followed by the Deep Code Review expert:
Congratulations, you’ve configured the native Gitlab integration and your first MR experts! 🎉