Integrations / Gitea / Forgejo

The coding agent for Gitea and Forgejo

If you run Gitea or Forgejo, most agent vendors do not even list you. FragonForge treats your instance as a first-class forge: label an issue, and the agent codes and tests the fix in an isolated sandbox, then opens a pull request for your review.

Start freeHow it works
the loop on Gitea / Forgejoillustrative example
queued   issue #86 labeled, verified
clone    git.example.com/acme/api
test     go test: 96 passed, 2 new
done     PR #87 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.

self-hosted Gitea and Forgejo instances

/api/v1

Your instance URL is required, whether you self-host or use a hosted Gitea or Forgejo service. Forgejo speaks the same API; both are supported identically. The token is validated live against your host before anything is saved.

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 Gitea / Forgejo

  1. Add the trigger label to an 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 pull 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

Is Forgejo really supported, or just Gitea?

Both, identically. Forgejo is API-compatible with Gitea, and FragonForge talks to both over /api/v1 with your instance URL and token.

My instance runs on a small VPS. Is that a problem?

No. FragonForge only calls your API and clones over HTTPS; the heavy lifting (agent, tests, sandbox) runs on our infrastructure. Your instance must be reachable from the internet, which a VPS typically is. Not sure? Run the same check as in the box above: curl -sI https://your-instance/ from a machine outside your network; if it answers, you are set.

Which plan do I need?

Any plan, including Free: 1 repository and 100 runs per month, no credit card. That is enough to try the loop on one real project.

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