GitLab

Version 1.0 · Last updated 2026-08-10

Context

GitLab bundles issue tracking in with the rest of the software delivery pipeline, so engineering teams file, triage, and close issues without leaving the tool they ship code from.

Closed GitLab issues flow into Living Knowledge as grounding content, so the agent learns from how your engineers actually described and fixed a problem, not a generic template of one. Because a fix in GitLab often lives partly in the issue and partly in the merge request that closed it, Living Knowledge draws on both instead of showing the agent only the tracker’s view. The Team Assistant works on top of GitLab itself, answering technical questions from Living Knowledge and a search of related issues, and when a person needs to pick one up, the agent opens an issue in GitLab where that’s supported, or falls back to email.

Key benefits

• Learn from how issues actually got fixed: Closed GitLab issues, and the merge requests that closed them, feed Living Knowledge, so the agent answers from real fixes rather than generic troubleshooting steps.
• Team Assistant on top of GitLab: Your team answers technical questions inside GitLab, drawing on Living Knowledge and related issues, without switching tools.
• Handover, your way: When a person is needed, the agent opens an issue in GitLab where that’s supported, or hands off by email, always with full context.

How does it work?

Unless pulls closed issues, and the merge requests linked to them, from GitLab into Living Knowledge, grounding the agent in how problems were actually solved. The Team Assistant then answers technical questions on top of GitLab using Living Knowledge and a search of related issues, and for handover opens an issue in GitLab where that’s supported, or routes by email.

Install instructions

Once at the Integrations tab of your Unless dashboard, you can select “Configure” for the GitLab integration. This will open a popup where you can connect your GitLab account and set up the integration.