Skip to content
Maestro Documentation

Projects

A Maestro project is a named record pointing to a Git checkout. The project key is used in the Dashboard, CLI, Telegram and Chat to keep work scoped.

Register a project

Section titled “Register a project”

From the Dashboard, open Projects and add a local path or repository URL. From a checkout:

Terminal window
maestro.cmd project add my-app C:\src\my-app
maestro.cmd project add my-app https://github.com/example/my-app
maestro.cmd project list

The URL form clones into a directory named after the key when that directory does not exist. Maestro detects the default branch where possible. A repository with no commits can be bootstrapped with a minimal README and .gitignore; a repository with existing uncommitted files is not silently changed.

Readiness rules

Section titled “Readiness rules”

Before a task is prepared, Maestro checks that:

  • the path exists and is a Git repository;
  • Git can read its status and base branch;
  • the source checkout is clean enough to create a worktree;
  • the configured execution root is available.

Use maestro.cmd doctor <project-key> for a deterministic report. The project path is local runtime state and is redacted from public evidence where appropriate.

Project scope

Section titled “Project scope”

Tasks and Chat threads are project-scoped by default. A separate Maestro (general) Chat context is available for provider and runtime questions without mixing project history.