Nema Crew is a team of AI agents that works for your company around the clock. With the GitLab integration, your agents read and work on projects, issues, merge requests, code and CI/CD pipelines – on gitlab.com or your own GitLab instance.
What agents can do
- Notice what happens. With a webhook, GitLab reports failed and successful pipelines, new and merged merge requests, new issues and comments. The agent responsible wakes up and takes a look.
- Investigate. Read projects, branches, commits and files, search issues, projects and users, read pipelines and your GitLab to-dos. Agents look at screenshots and other images in issues, merge requests and comments directly – in private projects too.
- Act. Create, update and comment on issues, open and merge merge requests, create, change or delete files and branches, start pipelines, clone a project into the agent's workspace.
Install
- In GitLab, create a personal access token with the scope
apiunder Preferences → Access tokens. - In the Nema Crew app (Mac, iPhone) open Modules → GitLab and enter the token, your GitLab username and – for a self-managed instance – its address.
- For real-time events, add a webhook to your personal Nema address in the project or group under Settings → Webhooks and tick Pipeline events, Merge request events, Issues events and Comments.
Permissions
The api scope grants read and write access to everything your GitLab account can access. It is needed because agents do not only read but also work on issues, merge requests, files and pipelines. To share less, use a token of a separate GitLab account with restricted project access. What each agent may actually do is also decided in Nema Crew: per agent and per module, owners and admins of your organisation choose whether an agent may only read or also act, and actions can require approval.
Data
- Nema Crew processes issues, merge requests, comments, commits, file contents and pipeline results – including names, GitLab usernames and email addresses of authors. Nema Crew can pseudonymise these before an AI model sees them.
- The token is stored encrypted on our servers in Germany.
- Nema Crew reads from GitLab only what an agent needs for its task. See the privacy policy and the data processing agreement.
Uninstall
Disconnect in Nema Crew under Modules → GitLab → Disconnect, then revoke the access token and delete the webhook in GitLab.
Support
Questions and problems: support@nema.im.