Integrations / Bitbucket Cloud

FragonForge on Bitbucket Cloud, honestly

Bitbucket Cloud is our narrowest integration right now. This page states exactly what works today and what does not, so you can decide without surprises.

Start free How it works

Bitbucket Cloud (bitbucket.org)

2.0 REST API

Bitbucket Cloud only; Bitbucket Server and Data Center are not supported. You connect with an app password, validated live before it is stored.

Paid plans include a monthly FragonForge AI budget in euros, so a run needs no key of your own. Point a repository at your own key instead and it spends that: Anthropic, OpenAI, Google, OpenRouter, Mistral, Groq, DeepSeek, or any OpenAI-compatible endpoint, billed by that provider at its list price. We never resell tokens or mark them up. Free carries no budget, so the loop above runs on your own key. A ChatGPT seat funds only the runs you start yourself, never the ones your forge triggers.

What works today, and what does not

Works today: pull-request webhooks start work automatically. An opened or updated pull request triggers analysis, a comment on a pull request dispatches agent feedback, and merges and declines update the run lifecycle on our side.
Works today: the agent can push branches, open and update pull requests, comment on them, and post commit statuses. Analysis scans with auto-fix pull requests also start from the dashboard.
Does not exist, and will not: the label-an-issue trigger. Bitbucket Cloud has no issue labels, so the trigger here is PR-based by design rather than issue-based.
If your issue tracking lives in Jira, read the FAQ below before connecting anything.

The honest version

If the label-an-issue loop is the reason you are here: Bitbucket Cloud has no issue labels, so that loop cannot exist on this forge. On Bitbucket, FragonForge is a PR-centered tool. We would rather say that now than after you connected a repo.

Frequently asked questions

When will the issue-label trigger work on Bitbucket?

It will not, and the reason is structural rather than a backlog position: Bitbucket Cloud has no issue labels to put on an issue. The trigger on Bitbucket is the pull request instead - opening, updating, or commenting on one dispatches work automatically.

What can I realistically do on Bitbucket today?

Connect a repository and let pull-request events drive it: opened and updated PRs run analysis, comments dispatch agent feedback, and auto-fix pull requests come out of the findings. Branch pushes, PR management, commit statuses, and dashboard-started scans all work. What you cannot do is start the coding loop from a Bitbucket issue.

Do you support Bitbucket Server or Data Center?

No, Bitbucket Cloud only.

We track issues in Jira, not Bitbucket. Does that change anything?

Honest answer: FragonForge has no Jira integration today, and on Bitbucket the trigger is PR-based by design, because Bitbucket Cloud has no issue labels. Jira-triggered runs would be an integration of its own, not a small extension. If that is what your team actually needs, write to office@fragonstudios.com and say so; that signal directly shapes what we build for Bitbucket users.

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