Projects
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.
A project is a codebase AI CodeOps works on. Every AI session belongs to a project, and the project collects what happens to that code over time: sessions, changes, deployments, incidents, SBOMs and decision records.
Create a project
- Open Plan → Projects and choose New project.
- Fill in the form (fields below).
- Choose Create project.
| Field | What to enter |
|---|---|
| Identifier | Lowercase, no spaces, for example billing-api. Used in URLs and reports. It can't change later. |
| Name | A readable name, for example "Billing API". |
| Type | service, library, frontend, infra, data pipeline, model, docs or other. |
| Repository URL | Optional. The repository's address, for example https://github.com/acme/billing-api. |
| Default branch | Optional. The branch sessions and the terminal work against. Blank means the repository's own default. |
| Test command | Optional. Run after a session writes code, against the proposed change, in an isolated environment. Blank means it is detected (a package.json test script, else pytest or go test). |
| Health check URL | Optional. A public https endpoint used by monitoring. |
| Description | Optional. |
Checking repository access
After entering a repository URL, choose Verify access. AI CodeOps tells you whether the repository is reachable and its default branch. If you have a connected Git account for that host, private repositories work: "Will use your GitHub account … private repos accessible." Without one, public repositories still clone, but you can't open pull requests.
Starting from scratch
Leave Repository URL empty to start a new codebase. Sessions then generate the source on the platform, and you can browse it under Develop → Source. When you want to ship it, choose Add repo on the project and enter a repository; later changes can then be opened as pull requests.
Turning off tests
Tick Don't run tests for this project if it has no test suite. Sessions then skip the test step, and the run page shows that the change wasn't verified. See Quality gates.
The project page
Open a project to see:
- Deployments, Open incidents, Vulnerable components (latest SBOM) and Recent ADRs at a glance;
- an Activity timeline of sessions, deployments, incidents and decisions;
- Recent deployments and Recent SBOMs.
From here you can Run workflow (describe a task and start a session on this project), Browse source, Edit the project, or Archive it.
Projects that show up in your SBOMs, decision records or incidents but aren't set up yet appear under Detected projects on the projects list, ready to add.
Archive and restore
Archive hides a project from the active list. Its history stays, but you can't run sessions against it. Archived projects are listed under Archived, with Restore to bring one back.
Next steps
Frequently asked questions
Can I create a project without a repository?
Yes. Leave the repository URL empty and the session's generated code stays on the platform. Add a repository later to ship it as a pull request.
Can I delete a project?
You can archive it. An archived project is hidden and can't run sessions, but its history stays and you can restore it.