MR enrichment
Add issue references, metadata, context, and summaries.
Early development
Your BOT for GitLab
Build secure, reusable GitLab automation on the CIBOT execution and control platform.
Respond to issues, merge requests, pipelines, and schedules without distributing automation logic or credentials across every repository.
Automation that responds to the GitLab lifecycle.
Turn GitLab events into focused CIBOT chores. Keep reusable logic in one place instead of rebuilding it in every repository.
>_ Event-driven automation
GitLab issues
Merge requests
Pipelines
Schedules
EVENT
▼
▼
CIBOT GITLAB CHORE
Issue
Merge request
Pipeline
Lifecycle sync
Move issues between development, testing, and completion.
Approval guard
Explain why a merge request cannot move forward.
QA feedback loop
Turn review feedback into a focused agent task.
Support work from issue to release.
Coding agents work inside individual tasks. Persistent automation can support the complete GitLab development lifecycle.
Issue
→Development
→Merge request
→Pipeline
→Approval
→Merge
→Release
CIBOT chores
link issueenrich MRupdate statusrequest reviewprocess QA feedbackverify approvalsprepare releaserun custom workflows
The agent completes the task. CIBOT chores keep the surrounding GitLab workflow moving.
Automations should not carry your secrets.
Run agents in isolated sandboxes. Give them scoped GitLab capabilities through a controlled access boundary.
Untrusted execution
ISOLATED SANDBOX / AI AGENT
No GitLab tokenNo cloud credentialsNo production secrets
capability request
▼
▼
Security boundary
CIBOT ACCESS PLANE
Read issuesUpdate statusCommentOpen merge requestInspect pipelineAudit action
GitLab API
Built on the CIBOT foundation.
GitLab BOT is a focused CIBOT use case. The reusable automation foundation will become open source when the CIBOT MVP is complete.
Help us keep building in the open.
GitLab BOT is part of the DistroOps open-source and commercial ecosystem. Partners help fund long-term development while the projects remain freely available under their open-source licenses.
Partners
Visibility across the Distro Ops open-source ecosystem. Including project websites and README files + presence on the central Distro Ops partner page.
Partner Slot #2
Partner Slot #3