Developer & CI · wired today
Drive GitLab with governed agents
Build, review and release state is where agents earn their keep. The GitLab connector is one of 205 executable connectors and gives agents 5 tools, with the credential held in the vault and every call receipted.
What agents can run against GitLab
| Tool | What it does |
|---|---|
list_issues | List issues in a GitLab project |
get_issue | Get details of a specific GitLab issue |
create_issue | Create a new issue in a GitLab project |
list_merge_requests | List merge requests in a GitLab project |
get_merge_request | Get details of a specific GitLab merge request |
What the GitLab connector needs
You provide private token from your GitLab account. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Where to get it: GitLab's own API documentation ↗ covers creating and scoping the credential.
How proven is this?
The GitLab connector is a hand-written module that has been exercised against the live GitLab API.
GitLab integration FAQ
What can Quox agents do with GitLab?
Agents can run 5 tools against GitLab: list issues, get issue, create issue, list merge requests, get merge request. Every call is receipted in the evidence trail.
What does the GitLab integration need?
You provide private token from your GitLab account. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Do agents see my GitLab credentials?
No. Credentials live encrypted in the Quox vault and are resolved server-side at call time. Agents invoke tools; they never receive the underlying secret.
How proven is the GitLab connector?
The GitLab connector is a hand-written module that has been exercised against the live GitLab API.