Total Task Executions
0
Issues & MR Notes processed
Successful Tasks
0
Code committed & merged
Active Coding Agents
0
Ready for webhook triggers
Currently Running
0
In queue or active workspace
🚀 Service Health & Status
Overview of active integration pipelines
🦊 GitLab Connection: Not Configured
🤖 Agents: Initializing
⚡ Webhook Endpoint: Ready (/api/webhooks/gitlab)
Recent Webhook Activity
| Status | Event | Target | Agent | Trigger User | Time | Action |
|---|---|---|---|---|---|---|
| Loading recent jobs... | ||||||
🤖 AI Coding Agents
Configure your AI coding agents, models, trigger labels, and system instructions.
🦊 GitLab Instance Configuration
Connect your self-hosted or cloud GitLab instance without requiring GitLab Ultimate.
📜 Execution Job Explorer
Audit history, live execution logs, and code modifications.
| Job ID | Status | Event | Project | Issue / MR | Agent | User | Started | Action |
|---|---|---|---|---|---|---|---|---|
| Loading jobs... | ||||||||
🔗 Complete GitLab Webhook Configuration Guide
Step-by-step instructions, token scopes, and required trigger events to enable autonomous AI agents.
🔑
Prerequisite: Create GitLab Access Token with Required Scopes
Before configuring webhooks, generate a Personal Access Token (PAT) or Project/Group Access Token in GitLab:
Where to create: In GitLab, go to User Settings ➔ Access Tokens (or Project/Group Settings ➔ Access Tokens).
| Required Scope | Why this scope is mandatory |
|---|---|
| api | Grants full read/write REST API access for creating Merge Requests, updating issue notes, adding award reaction emojis (👍, 👎), and resolving assignees. |
| read_repository | Allows the AI Agent worker to clone your repository files into an isolated workspace for analysis. |
| write_repository | Allows the AI Agent worker to push commits and feature branches directly to the remote repository. |
⚠️ Important: Ensure the token owner has at least Developer permissions on the target repositories so GitLab allows pushing commits and creating branches.
1
Navigate to Webhook Settings in GitLab
You can configure the webhook at the Project level (for a specific repository) or at the Group level (to automatically enable AI agents across all repositories in a team or organization):
Project Level: Go to your Repository ➔ Settings (left sidebar) ➔ Webhooks ➔ Click Add new webhook
Group Level: Go to your Group ➔ Settings (left sidebar) ➔ Webhooks ➔ Click Add new webhook
Group Level: Go to your Group ➔ Settings (left sidebar) ➔ Webhooks ➔ Click Add new webhook
2
Enter Webhook URL & Secret Token
💡 Tip: Clicking "Generate Random Token" creates a cryptographically secure 32-character token and automatically links it to your GitLab Settings.
3
Select Required Trigger Checkboxes
In the Trigger section of GitLab Webhook settings, configure the following checkboxes:
| GitLab Trigger | Status | Why this trigger is required |
|---|---|---|
| Issues events | ✅ Mandatory |
Essential for task pickup: Triggers when an issue is created or assigned an agent trigger label (e.g. ai-agent, antigravity, or claude-code). The service immediately acknowledges with 👍, creates the feature branch, opens the Merge Request, and assigns the user.
|
| Comments | ✅ Mandatory | Essential for MR feedback loop: Triggers when a developer leaves review feedback comments on the agent's Merge Request. The agent locks the comment with 👍, updates the codebase, commits, pushes, and summarizes the adjustments. |
| Confidential comments | ℹ️ Optional | Check this only if your repository processes private security notes or confidential MR feedback discussions. |
| Confidential issues events | ℹ️ Optional | Check this only if your team assigns AI agent labels to confidential/vulnerability issues. |
| Push events, Pipeline events, Wiki, Releases, etc. | ❌ Uncheck | Leave all other checkboxes unchecked to prevent unnecessary webhook traffic and avoid overloading your server. |
4
SSL Verification & Save
- 🔒 Enable SSL verification: Check this box if your service is behind HTTPS (reverse proxy with SSL / Cloudflare Tunnel / Traefik).
- 🚀 Click Add webhook at the bottom of the page in GitLab.
- 🧪 In GitLab under your newly created webhook, click Test ➔ Issues events. It should return HTTP 200 OK.
🧪 Interactive Webhook Simulator
Test how the service processes Issue webhook payloads directly in your browser.