# Quickstart: your first gated pull request > 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. Source: https://aicodeops.dev/docs/quickstart · Last updated: 2026-10-18 This guide takes you from a new account to your first AI-written change that passed its quality gates and became a pull request. It takes about ten minutes, most of it the session running. AI CodeOps is in open beta and free to use; it runs in your browser, so there is nothing to install. Each step has an **Open in AI CodeOps** link that takes you straight to the right screen (you sign in first if you need to). ## 1. Create your account (about 1 minute) Choose **Start free** on the site. Continue with GitHub or Google if they're offered, or sign up with your email and a password, then type the 6-digit code we email you. The code expires after 10 minutes. On your first sign-in, AI CodeOps creates a workspace for you. A workspace holds your projects, sessions, members and settings. If someone invited you, you join their workspace instead. Depending on your role, you may be asked to set up two-factor sign-in (an authenticator app or a passkey). See [Members and roles](https://aicodeops.dev/docs/members). ## 2. Connect your Git host (about 1 minute) AI CodeOps works on your repositories through your own Git account. 1. Open **Configure → Settings** and scroll to **Git Providers**. [Open in AI CodeOps](https://aicodeops.dev/open/settings) 2. Pick your host and choose **Connect**, or paste a personal access token and choose **Connect with token**. Guides for each host: [GitHub](https://aicodeops.dev/docs/git/github), [GitLab](https://aicodeops.dev/docs/git/gitlab), [Bitbucket](https://aicodeops.dev/docs/git/bitbucket), [Gitea](https://aicodeops.dev/docs/git/gitea), [Forgejo](https://aicodeops.dev/docs/git/forgejo). What each one is allowed to do: [Permissions and scopes](https://aicodeops.dev/docs/git/permissions-and-scopes). ## 3. Create a project (about 1 minute) 1. Open **Plan → Projects** and choose **New project**. [Open in AI CodeOps](https://aicodeops.dev/open/projects) 2. Enter an **Identifier** (like `billing-api`) and a **Name**. 3. Paste your **Repository URL** and choose **Verify access**, or leave it empty to start from scratch. 4. Choose **Create project**. Every session runs against a project. More in [Projects](https://aicodeops.dev/docs/projects). ## 4. Describe a change and start a session (under a minute, then it runs) 1. Open **Develop → AI Sessions** and choose **New session**. [Open in AI CodeOps](https://aicodeops.dev/open/sessions) 2. Describe a small, concrete task, for example "Add input validation to the signup endpoint and test it." 3. Keep the default workflow, **Plan, Build, Review & Test**, and pick your project. 4. Choose **Start session**. ## 5. Watch the agents plan, build and review (usually a few minutes) The session page shows each step live: the architect plans, the builder writes the change, a review reads the actual diff, and your project's tests run in a sandbox. It runs on the platform's models within your monthly allowance unless your workspace has its own provider key. See [How AI CodeOps works](https://aicodeops.dev/docs/how-it-works) and [Models and tiers](https://aicodeops.dev/docs/models). ![An AI session paused at the approval gate, with its changed files and review findings](https://aicodeops.dev/press/screenshots/02-session-release-gate.png) _Interactive demo, sample data._ ## 6. See the gate pass or fail (about 1 minute) When the session finishes, its page shows: - **Proposed changes**: the diff. - **Quality gates**: your tests' results and whether the change is release-ready. - **Findings**: anything the review flagged, with severity. An open high or critical finding blocks the change until it is fixed or triaged. The change also appears under **Develop → Changes**. More in [Quality gates](https://aicodeops.dev/docs/quality-gates). ## 7. Approve, and the pull request opens (about 1 minute) A review request is waiting under **Review & Gate → Approvals**. [Open in AI CodeOps](https://aicodeops.dev/open/approvals) When a teammate approves it and the gates pass, AI CodeOps opens a pull request on a new branch with the approver's Git connection. Working alone? You can approve your own change until someone else in the workspace can approve. You can then merge it on your Git host, or from the console, which checks the gate again first. See [Approvals and policies](https://aicodeops.dev/docs/approvals-and-policies). ## Next steps - [Invite your team](https://aicodeops.dev/docs/members) - [Set a budget](https://aicodeops.dev/docs/cost-controls) - [Set up AI CodeOps with your coding agent](https://aicodeops.dev/docs): every docs page is also Markdown at its URL plus .md - [See what's in each plan](https://aicodeops.dev/pricing) ## Frequently asked questions ### Does AI CodeOps cost anything during the beta? No. It is free during the open beta, with a monthly allowance of AI tokens on the platform's models. You can also connect your own model provider key. ### Do I need to install anything? No. AI CodeOps runs in the browser and sessions run on the platform. There is no CLI or desktop app to install. ### Can I try it without connecting a repository? Yes. Create a project with no repository URL and the agents start from scratch. You need a connected Git host to open a pull request.