AI CodeOps for Gitea

AI CodeOps works with Gitea servers you run. You connect Gitea 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 Gitea 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 Gitea 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 Gitea, open Settings → Applications and generate a token with read and write access to repository and read access to user. Copy it: Gitea shows it only once.
2. In AI CodeOps, open Configure → Settings → Git Providers and enter your server's public https address in the Gitea card's Instance URL. It is required.
3. Paste the token and choose Connect with token. AI CodeOps checks it against your server before saving it.

Connect via OAuth works only for the one server the platform's OAuth app is registered on, so for your own server use a token. The address can't be on a private network, localhost, or a .local or .internal name, and it can't carry a query string or #fragment.

The full steps, scopes and error messages are in Connect Gitea. 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 Gitea.

Why teams use it with Gitea

Most AI coding tools are built around one or two big hosted Git services. Teams who chose Gitea to keep their code close get the same AI workflow here, against their own server.

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 Gitea 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 Gitea. 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/gitea