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 | Project | Issue / MR | Agent | User | Time | Action |
|---|---|---|---|---|---|---|---|
| Loading recent jobs... | |||||||
🤖 AI Coding Agents
Configure your AI coding agents, models, trigger labels, and system instructions.
📖 Agent Setup & API Key Guide
How to obtain API keys and configure each supported AI coding provider.
✨ Google Antigravity (Gemini)
Free Tier Available
Connects directly to Google's Gemini models via the official Google GenAI SDK.
- Get API Key: Google AI Studio ↗
- Recommended Models:
gemini-2.0-flash,gemini-1.5-pro - Default Trigger Labels:
ai-agent,antigravity,gemini - Base URL: Leave empty (uses official endpoint)
🧠 Claude Code (Anthropic)
State-of-the-Art
Uses Anthropic's Claude 3.7 Sonnet for precise code refactoring and multi-file edits.
- Get API Key: Anthropic Console ↗
- Recommended Models:
claude-3-7-sonnet-20250219,claude-3-5-sonnet-20241022 - Default Trigger Labels:
claude,claude-code,anthropic - Base URL: Leave empty (uses official endpoint)
⚡ OpenCode (Docker / Server)
Local & Cloud
OpenCode runs as an autonomous coding container service in your Docker network.
- Docker Image:
ghcr.io/anomalyco/opencode:latest - Base URL:
http://opencode:4096(Docker) orhttp://localhost:4096 - Recommended Models:
zen,qwen2.5-coder-32b,deepseek-coder - Default Trigger Labels:
opencode,qwen - API Key: Optional (only needed if auth is enabled)
🦙 Custom / Ollama / vLLM
Self-Hosted
Compatible with local OpenAI-compatible endpoints (Ollama, vLLM, LiteLLM).
- Ollama Base URL:
http://host.docker.internal:11434/v1 - vLLM Base URL:
http://vllm-host:8000/v1 - Models:
qwen2.5-coder:32b,deepseek-coder-v2 - Default Trigger Labels: custom (e.g.
local-llm,ollama)
🦊 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.
⚡ Automated 1-Click Webhook Sync (No Manual Setup Required)
You don't need to manually configure webhooks in dozens of repositories! Click the button to automatically attach the required webhooks to all GitLab projects accessible to your bot account.
🔑
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. |
| Pipeline events | ✨ Recommended (Auto-Repair) | Autonomous CI Self-Healing: Triggers when a CI Pipeline on an agent branch or Merge Request fails. The agent downloads failed job console logs/traces, diagnoses the error (e.g. failing unit tests, linter errors, missing imports), modifies the code in the workspace, commits a fix, and reports back on the MR (protected with a max-3-attempts loop guard). |
| 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, Wiki, Releases, etc. | ❌ Uncheck | Leave 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.
5
Instance-Wide System Hook (Auto-Register on Project Creation)
If you run a self-hosted GitLab instance (CE/EE), you can configure a System Hook so newly created repositories are automatically connected without any manual work:
Where to configure: In GitLab Admin Area ➔ Overview (or Settings) ➔ System Hooks (
URL: Paste your Webhook URL (
Secret Token: Paste your configured Webhook Secret Token
Trigger: Check ✅ Repository update events / Push events
/admin/hooks)URL: Paste your Webhook URL (
.../api/webhooks/gitlab)Secret Token: Paste your configured Webhook Secret Token
Trigger: Check ✅ Repository update events / Push events
✨ How it works: Whenever a new project is created on your GitLab server, GitLab sends a
project_create system hook event. The AI Agent Service intercepts this event and automatically registers the project webhook with all required issue, note, and CI triggers on that new project!
🧪 Interactive Webhook Simulator
Test how the service processes Issue webhook payloads directly in your browser.
👥 User Management
Manage colleague access, accounts, and administrator permissions.
| User ID | Username | Role | Created At | Actions |
|---|---|---|---|---|
| Loading users... | ||||