A Coder project is a scoped workspace that gives a run everything it needs: the repository, relevant docs, the deployment target, and the project's constraints.
Why projects matter
Coder works inside your existing repository rather than a separate copy. A project makes that repository plus its context explicit so a run stays focused and reviewable.
What a project contains
- Repository*: the Git repo Coder reads, branches, commits, and opens pull requests in.
- Docs and context*: product specs, architecture notes, and runbooks the run should respect.
- Deployment target*: where a finished result should go (local only today; cloud deployment is planned).
- Constraints*: language, framework, test, and approval rules the run must follow.
Creating a project
Start from the Coder surface or the native UI and point Coder at your repository. Coder reads the project's structure and proposes an initial task queue from the mission you provide.
Company and role scope
A project runs in your Ottili company context. Access and audit follow the same company and role model as the rest of the platform, so a run can only touch what your role permits.
Related
- Turn a project into a [mission](/docs/coder-missions).
- See how runs stay in your [Git workflow](/docs/coder-git).
Was this article helpful?