GitLab

• “Which issues in the Law-firm portal project are open?”
• “Summarize the discussion on issue 231.”
• “Which merge requests are waiting for review?”
• “What has happened in our projects since Monday?”
• “Find all issues with the Privacy label.”

The assistant can list projects and look them up one by one, search issues across all projects or in one project, read comment threads of issues and merge requests and start a search across the instance.

1. 01Click your avatar at the top right and choose Edit profile.
2. 02On the left under Access open Personal access tokens.
3. 03Under Generate token choose Legacy token.
4. 04Give a name, set an expiry date and tick only read_api. anymize needs nothing more.
5. 05Click Generate token and copy the value immediately. It is shown only once.

1. 01In anymize open Apps, then Connectors, and choose GitLab.
2. 02Enter your instance address, for example https://gitlab.your-company.com. For gitlab.com enter https://gitlab.com.
3. 03Paste the personal access token from the section above and click Connect. anymize immediately checks which account it belongs to.
4. 04Then you set which areas the assistant may use: account, projects, issues, merge requests.

You create the token yourself, without an administrator and without approval from GitLab. The path via GitLab's own AI connection would be a different one; it also requires GitLab Duo. You do not need that here.

No. There is no tool that creates an issue, writes a comment, sets a label or merges anything. The connection sends read requests only.

That is not built as a setting but as a rule in the build: no tool name may carry a write verb, a test records that. If a write tool were ever added, GitLab would have to lose the “Read only” label. You can also cut the token with read_api so tightly from the start that GitLab itself does not allow writing.

GitLab can be self-hosted. When connecting you give the address of your own instance, and anymize talks exactly to that address, to no other. For municipalities, authorities and companies with their own server landscape that is the decisive point: the source code stays where it is.

• No creating an application at the vendor, no approval process.
• The token is stored encrypted in your workspace and used only for your requests.
• If you disconnect, access is gone immediately.

• Search source code and commits: these search areas require GitLab Premium plus Elasticsearch. Without that you get an empty list back, not an error.
• Pipelines, releases and wiki pages are not included at this stage.
• A list returns at most 50 entries per page so a conversation is not buried in raw data.

Text that goes through is anonymized: names of authors and editors, email addresses and customer names in issue texts are replaced by placeholders before an AI model reads them.