AI CodeOps for Forgejo

AI CodeOps works with Forgejo servers, your own or a public instance such as Codeberg. (On Codeberg, check its Terms of Use first: they don't allow projects that mostly consist of code written by generative AI tools.) You connect Forgejo once, then describe a change in the browser. Agents plan it, write it, review it and run the project's tests, and the result arrives in Forgejo as a pull request that has already passed your quality gates.

What the integration does

• Repositories: Develop → Repositories lists the repositories the connected account can see, with their branches, files and pull requests.
• Projects: a project points at one repository. Sessions in that project clone it, write the change and test it in a sandbox. See projects.
• Branches and pull requests: when a change is approved and passes the release gate, AI CodeOps pushes a branch named codeops/run-<id> and opens a pull request into the project's default branch. Commits are authored as "AI CodeOps".
• Merging: a pull request the console opened can be merged from the console, and the release gate runs again first. You can also merge it in Forgejo as usual.

AI CodeOps doesn't install webhooks, post commit statuses or comment on your pull requests. It never pushes to your default branch directly.

How to connect

1. In Forgejo, open Settings → Applications and generate an access token with read and write on repository and read on user. On Codeberg, that's your Codeberg account settings.
2. In AI CodeOps, open the Forgejo card under Configure → Settings → Git Providers and enter the server's public https address as the Instance URL, for example https://codeberg.org.
3. Paste the token and choose Connect with token.

For your own server, use a token: OAuth only works for the server the platform's OAuth app is registered on. AI CodeOps doesn't read Forgejo Actions results either; tests run in the session's own sandbox before the pull request is opened.

The full steps, scopes and error messages are in Connect Forgejo. Tokens are encrypted at rest (AES-256-GCM) and never written into a repository's Git configuration. To remove access, disconnect in AI CodeOps or revoke the token in Forgejo.

Why teams use it with Forgejo

Forgejo users care about owning their tooling. AI CodeOps keeps the work on your server: the branch and pull request live there, commits are authored as AI CodeOps, and no webhook is installed.

Every change carries its history with it: which model wrote it, what the reviewers found, which tests ran and who approved it. That history is kept as a signed evidence pack you can hand to an auditor. Spend is visible per session and capped per workspace, so an agent can't run up a bill unseen. See cost controls.

Getting started

1. Create a free account: AI CodeOps is in open beta and runs in your browser.
2. Connect Forgejo from Configure → Settings → Git Providers.
3. Create a project from a repository and run a first session. The quickstart walks through it.

AI CodeOps also works with the other Git hosts, so a team that uses more than one can run them all from one workspace.

For partners

AI CodeOps is a browser-based platform where AI agents plan, write, review and test code changes and open them as pull requests on Forgejo. Changes merge only after tests, an AI review and the required approvals pass, and each one keeps a signed record of how it was made. Free during its open beta: https://aicodeops.dev/integrations/forgejo