AI CodeOps

AI CodeOps for GitHub

Run AI CodeOps on your GitHub repositories: agents write the change on a branch, open a pull request, and it merges only after your quality gates pass.

AI CodeOps works with GitHub.com. You connect GitHub 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 GitHub 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 GitHub 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

Connect with GitHub OAuth in a couple of clicks, or paste a personal access token: a classic token with the repo scope, or a fine-grained token with Contents and Pull requests set to read and write.

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

Why teams use it with GitHub

If your organisation restricts OAuth apps, an organisation owner may need to approve AI CodeOps before its repositories appear. A fine-grained token scoped to just the repositories you choose is the narrowest option.

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 GitHub 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 GitHub. 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/github

Frequently asked questions

Does AI CodeOps need admin access to our GitHub?

No. It needs an account that can read the repositories you want to use, push a branch and open pull requests. The connection belongs to the person who made it.

Does AI CodeOps work with GitHub Enterprise Server?

No. The GitHub connection is for GitHub.com only. If you run your own Git server, AI CodeOps connects to GitLab, Gitea and Forgejo instances.

Which scopes does the GitHub connection ask for?

OAuth asks for repo, read:user and user:email. A fine-grained token needs Contents and Pull requests set to read and write.

Can a pull request merge before it passes the gate?

Not through AI CodeOps. A pull request it opened can be merged from the console only after the release gate passes again: tests, AI review findings and approvals.