User guideAI Engineering Platform
Back to siteSite

Projects and blueprints

A blueprint is the only entry point for creating a project. It captures the decisions that should not be reinvented for every repository.

What a blueprint contains

  • stack and repository layout
  • test strategy and required checks
  • design standards and component registry references
  • default agents and allowed models
  • starter tasks and acceptance templates
  • project rules and approval requirements

Blueprints

Published templates and versioned project blueprints.

Create a blueprint version

  1. Open Blueprints.
  2. Choose a template or + New blueprint.
  3. Edit the definition: stack, test strategy, agents, rules.
  4. Save a version. Versions are immutable.
  5. Review the diff and Publish.

A published version can be instantiated by projects. Draft versions are visible only to the team.

Create a project

  1. Open Projects → New project.
  2. Name the project and select the blueprint version.
  3. Connect the Git repository:
    • install the GitHub App for the repository, or
    • connect a GitLab project, or
    • use a token for a local repository.
  4. Choose the default branch and the agent/model allowed for the project.
  5. Create the project.

The project inherits the blueprint's test strategy, rules and starter tasks. You can override values per project, but the blueprint version used at creation is recorded.

Repositories

The Repositories view shows the connected repositories and their status. A repository must be reachable by the worker before a run can clone it.

For GitHub, the App installation grants access to selected repositories. For GitLab, the connection is scoped to a project. Tokens are stored encrypted and never returned by the API.

Project settings

SettingEffect
Required checksChecks that must be green before a PR can merge
E2E commandCommand run after unit tests in the sandbox
Required approvalsNumber of distinct approvers for a PR
Merge windowTime window in which the merge queue may land changes
MCP serversTrusted tool servers available to runs
Agents and modelsProviders and agent plugins allowed in the project

Permissions

  • Owner/Admin can create, edit and archive projects and blueprints.
  • Member can work with tasks and runs in projects they can access.
  • Viewer can read the board, runs and results.

Limits and good practice

  • Keep a blueprint small enough to review; put product-specific detail in tasks.
  • Publish a new version instead of editing a published one.
  • Connect only the repositories the project needs.
  • Use project-level rules when a client or repository needs stricter controls.

Next

The per-project test command

Each project sets the command the development run must pass (go test ./..., pnpm test, ...). The run executes it in the sandbox; a red command fails the run and starts a CI-fix flow.

Set it in the project settings, or in the /setup wizard's third step. A new blueprint's starter task inherits the project's test command.