# Core concepts

> The building blocks of AI CodeOps: organizations, workspaces, projects, agents, workflows, sessions, findings, gates, approvals, changes and deployments.

Source: https://aicodeops.dev/docs/core-concepts · Last updated: 2026-10-18

These are the things AI CodeOps works with, and how they connect. Each entry says where to find it in the console.

## Organization

The account that owns workspaces, and the unit for plan and seats. Everyone gets an organization the first time they sign in. Manage it under **Configure → Settings → Organization & Teams**.

## Workspace

Where your team works: projects, sessions, members, roles and settings. Every workspace belongs to one organization. Workspaces are kept apart in the database, so one can't read another's data. See [Members and roles](https://aicodeops.dev/docs/members).

## Project

A codebase AI CodeOps works on, usually linked to a Git repository. It has an identifier, a type, a default branch and a test command. Every session runs against a project. Find projects under **Plan → Projects**. See [Projects](https://aicodeops.dev/docs/projects).

## Agent

An AI role with its own instructions, such as Architect, Builder, Reviewer, Tester or Security Auditor. Each step of a workflow is run by one agent. You can define your own agents with their own model, permissions and prompt under **Configure → Agents**. See [Agents and workflows](https://aicodeops.dev/docs/agents) and the [agent pages](https://aicodeops.dev/agents).

## Workflow

A fixed list of steps, each run by one agent, for example Plan → Build → Review → Test. There are 16 built-in workflows, listed under **Develop → Workflows**. See [Workflows](https://aicodeops.dev/docs/workflows).

## Session

One run of a workflow on one task and one project. In the console it's an **AI session**, under **Develop → AI Sessions**. A session records each agent step, its tokens and cost, the diff it produced and its test result.

A session's status is one of: pending, running, completed, failed, canceled, or blocked (by a policy or a budget). A follow-up session is linked to the session it builds on.

## Finding

An issue the AI review found in a change. Each finding has:

- a **severity**: critical, high, medium, low or info;
- a **category**, such as security, quality, performance or test coverage;
- a **triage status**: open, acknowledged, in progress, fixed, won't fix, false positive or duplicate.

Open high and critical findings block the change. Findings appear on the session page and under **Build & Test → Quality**. See [Multi-agent reviews](https://aicodeops.dev/docs/multi-agent-reviews).

## Quality gate

The check that decides whether a change can ship. A change is release-ready when its review completed, no high or critical finding is still open, and no test failed. The gate runs before a pull request opens and before the console merges one. Your CI can ask the same question through the release gate. See [Quality gates](https://aicodeops.dev/docs/quality-gates).

## Approval

A request for a person to say yes or no. AI CodeOps opens one for every code change a session proposes, and for actions your policy marks ask. Each has a status: pending, approved, rejected, expired or canceled. Decide them under **Review & Gate → Approvals**. See [Approvals and policies](https://aicodeops.dev/docs/approvals-and-policies).

## Change

The unit of work, from proposal to production. A change links the session that made it, its approval, its pull request, its deployment and any incident. Its status moves forward:

| Status    | Meaning                                        |
| --------- | ---------------------------------------------- |
| proposed  | A session started on it.                       |
| in review | The session produced code; it awaits approval. |
| approved  | A person approved it.                          |
| merged    | Its pull request was merged from the console.  |
| deployed  | A deployment of it succeeded.                  |
| abandoned | The session failed or was canceled.            |

Find changes under **Develop → Changes**.

## Evidence pack

A signed record of how one change was made: the task, models, approvals, policy decisions, findings, tests and delivery. Download it from a change's page and verify it in the browser or offline. See [Evidence packs](https://aicodeops.dev/docs/evidence-packs).

## Deployment

A record that a version of a project went to an environment. It has a status (queued, in progress, succeeded, failed, rolled back or canceled), a commit or version, and the session that produced it. Find deployments under **Release → Deployments**. See [Gated deploys](https://aicodeops.dev/docs/gated-deploys).

## Next steps

- [How AI CodeOps works](https://aicodeops.dev/docs/how-it-works)
- [Start a session](https://aicodeops.dev/docs/sessions)
- [Open beta FAQ](https://aicodeops.dev/docs/open-beta-faq)

## Frequently asked questions

### Is a session the same as a workflow?

No. A workflow is the recipe, a fixed list of agent steps. A session is one run of a workflow on one task and one project.

### Where do I find a change after its session ends?

Under Develop → Changes. A change follows the work from proposal through review, merge and deployment.

### Does AI CodeOps deploy my code?

No. It calls a deploy webhook you set and records the deployment. Your own pipeline does the deploy.