Overview

Projects are blueprints for development environments. They connect a repository to runners with predefined configurations, enabling team members to create fully configured environments with one click. This ensures all team members work with the same standardized setup.

Prerequisites

• At least one runner in your organization
• By default, all organization members can create projects
• Admins can restrict project creation to admins only via Settings → Policies → “Only admins can create projects”

Create a project

1. Go to your organization dashboard
2. Click Create project

3. Enter the repository URL
4. Enter a project name
5. Select at least one environment class

Configuration options

Option	Description
Repository URL	Git repository cloned when creating environments
Repository branch	Default branch checked out (e.g., main, develop)
Environment classes	Compute resources (CPU, memory, storage) and region. Min 1, max 30 per project
Dev Container path	Path to devcontainer configuration file
Tasks and services	Path to automation YAML file
Recommended editors	Editors and versions suggested for this project

Environment classes

Each runner has multiple environment classes configured (e.g., Small, Regular, Large). When you select environment classes for a project, you’re choosing which compute configurations are available to users creating environments.

Dev Container configuration

Specifies how the development container is configured:

• Base image
• VS Code extensions
• Environment variables
• Port forwarding rules

See Dev Container configuration for details.

Tasks and services

Define automated workflows beyond Dev Container setup:

• Services: long-running processes (databases, servers)
• Tasks: one-off actions (test runs, builds)
• Automations: database provisioning, cloud authentication

See Tasks and services for details.

Recommended editors

Configure which editors and versions are suggested for your project. When team members open an environment, they’ll see these recommendations.

Editor aliases:

• vscode - VS Code Desktop
• vscode-browser - VS Code in browser
• cursor - Cursor
• intellij, goland, pycharm, webstorm, phpstorm, rubymine, clion, rider, datagrip - JetBrains IDEs
• zed - Zed

Version configuration:

• Specify version numbers to recommend specific releases (e.g., 2025.1, 2024.3 for JetBrains)
• Leave versions empty to recommend all available versions of an editor

This setting helps standardize tooling across your team and ensures compatibility with project-specific configurations.

Manage projects

Select a project from your organization dashboard to modify its settings:

• Environment classes
• Dev Container and tasks/services paths
• Recommended editors
• Project secrets

Limitations

Multi-repo configurations aren’t built-in. See Working with multiple repositories for a workaround.

Next steps

• Create an environment from your project
• Share the project with your team
• Add project secrets