GitLab
Connect GitLab and your agents can read repos, search issues and merge requests, and summarize what actually changed across your projects. They can comment, open issues and update MRs with human-in-the-loop approval, and fire workflows when a pipeline fails.
What your agents can do with GitLab
- Read repos, issues and merge requests
- Summarize pipeline runs and failures
- Comment and triage issues (with approval)
- Trigger workflows on push or MR events
How to connect GitLab to Velaris
- 1
Create your Velaris account
Sign up and open your AI OS desktop.
- 2
Open Connections
Go to Settings → Connections in the OS.
- 3
Connect GitLab
Authorize GitLab with scoped access you control.
- 4
Ask an agent to act
Tell Velaris a goal — it uses GitLab from the mesh automatically.
Popular ways to use it
GitLab + Velaris — common questions
Does Velaris work with self-hosted GitLab?
Yes — point the connection at your own GitLab instance URL and authenticate with a project or personal access token. The same reads, approval-gated writes and triggers apply.
Can an agent merge a merge request on its own?
No. Merging is a destructive-tier action — the agent stages the merge, shows you the branch and diff, and waits for your explicit approval before anything lands.
What GitLab permissions does the connection need?
A read_api scope covers every automatic read: repos, issues, merge requests and pipelines. The wider api scope is only needed for commenting and updates, which still route through approval.