Integrations / GitLab

The coding agent for your GitLab

gitlab.com or your own instance: label an issue, and FragonForge plans, codes, and tests the fix in an isolated sandbox, then opens a merge request for your review. GitLab is our most complete integration.

Start freeHow it works
the loop on GitLabillustrative example
queued   issue #412 labeled, verified
clone    gitlab.example.com/acme/api
test     dotnet test: 214 passed, 2 new
done     MR !391 opened, awaiting review

Reachability check before you invest setup time: FragonForge is a hosted service and calls your forge's API from our infrastructure. Your instance must be reachable from the internet; one that is only reachable inside a VPN or private network cannot be connected today. A quick self-check: if curl -sI https://your-instance/ answers from a machine outside your network (a phone hotspot works), you are reachable. On the Enterprise tier, a deployment on your own hardware can be arranged by agreement.

gitlab.com and self-managed instances

/api/v4

For a self-managed instance you add your API endpoint once per organization. The token is validated live against your host before anything is saved, and the app shows you the exact token scopes it needs when you connect.

Every run spends your own LLM key: Anthropic, OpenAI, Google, OpenRouter, Groq, DeepSeek, or any OpenAI-compatible endpoint. We never resell tokens or mark them up.

The loop on GitLab

  1. Add the trigger label to a GitLab issue. FragonForge receives the webhook and verifies both the signed URL token and your webhook secret.

  2. The agent works in an isolated per-run Kubernetes sandbox: it reads the issue, inspects the code, writes the fix, and runs your test suite.

  3. It pushes a branch and opens a merge request with a description of what it did and why, and comments on the issue.

  4. You review and merge. FragonForge never merges on its own.

Frequently asked questions

Does it work with a self-managed GitLab instance?

Yes, that is the primary use case. You supply your instance's URL and a token; both are validated live before they are stored. One requirement: the instance must be reachable from outside your network, because FragonForge is a hosted service. A GitLab that is only reachable inside a VPN cannot be connected today.

Which plan do I need for self-managed GitLab?

Any plan, including Free. Forge support is never a paid feature.

What does FragonForge do on GitLab besides opening merge requests?

It comments on the triggering issue, updates the merge request on retries, and runs the analysis plane: static analysis with a baseline-aware quality gate and optional auto-fix merge requests.

We already have GitLab Duo. Why FragonForge?

Maybe you do not need us; Duo has an issue-to-MR agent too. The differences that matter: your own LLM key and contract from day one, flat per-organization pricing, full support for GitLab CE, and the same loop on GitHub and Gitea, plus a PR-centered integration on Bitbucket. There is an honest side-by-side at /compare/gitlab-duo/.

Try it on one repository

Free plan: 1 repository, 100 runs per month, hard stop, no credit card. Isolation architecture on the security page.

Start free