# AI CodeOps documentation > AI CodeOps (formerly CodeOps Studio) is a browser-based platform where AI agents plan, build, review, test and ship code, and nothing merges until quality gates and a human approve it. These pages explain how to use it; every page is also available as Markdown at its URL plus .md. Everything in one file: https://aicodeops.dev/docs/llms-full.txt API (OpenAPI 3.1): https://aicodeops.dev/docs/api/openapi.json ## Get started - [Quickstart: your first gated pull request](https://aicodeops.dev/docs/quickstart.md): Go from sign-up to your first AI change that passed its quality gates and opened a pull request: account, Git, project, session, approval. About ten minutes. - [How AI CodeOps works](https://aicodeops.dev/docs/how-it-works.md): Follow one AI CodeOps session from task to merged pull request: agents plan and build, your tests run in a sandbox, AI review flags issues, a person approves. - [Core concepts](https://aicodeops.dev/docs/core-concepts.md): The building blocks of AI CodeOps: organizations, workspaces, projects, agents, workflows, sessions, findings, gates, approvals, changes and deployments. - [Open beta FAQ](https://aicodeops.dev/docs/open-beta-faq.md): What the AI CodeOps open beta includes: free use, the monthly AI token allowance, your own model key, how your code and data are handled, and what comes after. ## Connect your code - [Connect your Git provider](https://aicodeops.dev/docs/git.md): Which Git hosts AI CodeOps works with (GitHub, GitLab, Bitbucket, Gitea and Forgejo), how each one connects, and what the platform does in your repositories. - [Connect GitHub](https://aicodeops.dev/docs/git/github.md): Connect a GitHub.com account to AI CodeOps with OAuth or a personal access token, the scopes it needs, and what the platform does with your repositories. - [Connect GitLab](https://aicodeops.dev/docs/git/gitlab.md): Connect GitLab.com or a self-managed GitLab instance to AI CodeOps with OAuth or a personal access token, and see how merge requests are opened for you. - [Connect Bitbucket](https://aicodeops.dev/docs/git/bitbucket.md): Connect a Bitbucket Cloud account to AI CodeOps with OAuth so sessions can push branches and open pull requests, plus the limits of token-based connections. - [Connect Gitea](https://aicodeops.dev/docs/git/gitea.md): Connect your own Gitea server to AI CodeOps with a personal access token: the instance URL, the token scopes it needs, and how pull requests are opened for you. - [Connect Forgejo](https://aicodeops.dev/docs/git/forgejo.md): Connect a Forgejo server, such as Codeberg or your own instance, to AI CodeOps with a personal access token, and see what the platform does with your repos. - [Projects](https://aicodeops.dev/docs/projects.md): Create a project in AI CodeOps: link a Git repository or start from scratch, set the default branch and test command, and see what a project tracks over time. - [Git permissions and scopes](https://aicodeops.dev/docs/git/permissions-and-scopes.md): The OAuth scopes and token permissions AI CodeOps asks for on GitHub, GitLab, Bitbucket, Gitea and Forgejo, what each is used for, and how to revoke access. ## Agents - [Agents and workflows](https://aicodeops.dev/docs/agents.md): The AI agents that run in an AI CodeOps session and the 16 built-in workflows that order them, from Plan, Build, Review & Test to Incident Response. - [Models and tiers](https://aicodeops.dev/docs/models.md): Choose how AI CodeOps sessions get a model: the platform's Economy, Standard and Premium tiers or Auto within your plan's allowance, or your own provider key. ## Workflows & quality gates - [Sessions](https://aicodeops.dev/docs/sessions.md): Start an AI session in AI CodeOps: describe the task, pick a project and workflow, watch the agents work live, review the diff, and open a pull request. - [Workflows](https://aicodeops.dev/docs/workflows.md): The 16 built-in AI CodeOps workflows and their steps, plus how to start one, schedule it, re-run it, cancel it, and build on a finished session with follow-ups. - [Quality gates](https://aicodeops.dev/docs/quality-gates.md): How AI CodeOps decides whether a change can ship: test results, the AI findings review, approvals, and the release gate check your CI can call. - [Approvals and policies](https://aicodeops.dev/docs/approvals-and-policies.md): Set what AI sessions may do with workspace policy rules (allow, ask, deny) and how human approvals work: who can approve, expiry, and rejections. - [Multi-agent reviews](https://aicodeops.dev/docs/multi-agent-reviews.md): How AI CodeOps reviews a change with several agents: review steps, a findings pass over the real diff, severity and triage, and the human approval that follows. ## Security & supply chain - [Security and SBOM](https://aicodeops.dev/docs/security-and-sbom.md): How AI CodeOps handles security findings, SBOMs per project (CycloneDX and SPDX), license checks in the release gate, sandboxed terminals and encrypted secrets. - [Dependency audit](https://aicodeops.dev/docs/dependency-audit.md): Run the Dependency Auditor agent on your project, see what it reads and reports, and how its findings land in the review that gates the pull request. - [Policy rules reference](https://aicodeops.dev/docs/policy-engine.md): Write workspace policy rules for AI sessions: the seven actions, allow, ask and deny, resource globs, trust postures, log-only mode, and a worked example. - [Evidence packs](https://aicodeops.dev/docs/evidence-packs.md): Download a signed record of how one change was made (task, models, approvals, findings, tests, delivery) and verify it in the browser or offline. ## Deploy - [Gated deploys](https://aicodeops.dev/docs/gated-deploys.md): How AI CodeOps hands a merged change to your deploy pipeline: the quality gate before merge, deploy webhooks, policy rules per environment and deploy records. - [Roll back a deployment](https://aicodeops.dev/docs/rollback.md): What rollback means in AI CodeOps: you roll back in your own deploy pipeline, then mark the deployment rolled back so history and failure rate stay accurate. ## Cost & usage - [Cost controls](https://aicodeops.dev/docs/cost-controls.md): Cap AI spend in AI CodeOps with a workspace budget and per-workflow caps, see cost per session and per step, and read the Usage page's allowance and charts. - [Usage and spend](https://aicodeops.dev/docs/usage-and-spend.md): See what AI CodeOps spends: cost per session and per agent step, cost by agent across sessions, the Usage page's allowance, daily cost and call history. ## Admin - [Members and roles](https://aicodeops.dev/docs/members.md): Invite people to an AI CodeOps workspace, choose built-in roles from owner to viewer, create custom roles on Enterprise, and require two-factor sign-in. - [Roles and permissions](https://aicodeops.dev/docs/roles-and-permissions.md): Every built-in AI CodeOps role and what it can do: who starts sessions, who approves changes, who edits policies, plus custom roles and how roles are assigned. - [Audit logs](https://aicodeops.dev/docs/audit-logs.md): What the AI CodeOps audit log records, how to read and filter it under Measure → Audit Log, who can see it, and how long entries are kept on each plan. - [Set up single sign-on (SSO)](https://aicodeops.dev/docs/sso.md): Set up SAML 2.0 or OpenID Connect sign-in for AI CodeOps on the Enterprise plan: verify your domain, create a connection, configure your IdP and activate it. - [Data retention and deletion](https://aicodeops.dev/docs/data-retention.md): How long AI CodeOps keeps sessions, audit records, delivery logs and backups, how to export your account data, how deletion works, and how your code is used. ## Enterprise - [Enterprise overview](https://aicodeops.dev/docs/enterprise.md): What the AI CodeOps Enterprise plan adds: SSO with SAML or OIDC, custom roles, audit history kept for the life of your organization, and self-hosting. - [Self-hosted deployment](https://aicodeops.dev/docs/self-hosted.md): An overview of running AI CodeOps on your own Kubernetes cluster, an Enterprise option on request: what it involves, what it needs, and how to get started. ## Developers - [API](https://aicodeops.dev/docs/api.md): What you can call programmatically today: the release gate check for CI with a workspace API key, and the public evidence pack keys. The API is limited in beta. - [Webhooks](https://aicodeops.dev/docs/webhooks.md): Send AI CodeOps events to Slack, Discord, Teams or your own HTTPS endpoint, verify signed payloads, and call your deploy pipeline when a change merges. - [MCP servers](https://aicodeops.dev/docs/mcp-servers.md): Connect remote MCP servers so AI CodeOps agents can call their tools: add a server, keep its headers encrypted, and limit tools per agent and by policy. - [The AI CodeOps MCP server](https://aicodeops.dev/docs/mcp-server.md): Connect Claude Code, Cursor or any MCP client to AI CodeOps: start sessions, read findings, check the release gate and fetch evidence packs from your editor. ## Help - [Troubleshooting](https://aicodeops.dev/docs/troubleshooting.md): Fixes for common AI CodeOps problems: Git connections, sessions that stop on allowance or budget, pull requests that won't open, missing pages and sign-in. - [Frequently asked questions](https://aicodeops.dev/docs/faq.md): Short answers about AI CodeOps: what it does, what it costs in the open beta, which Git hosts and models it supports, and how it handles your code and data. - [Contact support](https://aicodeops.dev/docs/contact-support.md): Get help with AI CodeOps: ask the in-console Help assistant, open a support ticket, email the team, check the status page, or report a security issue.