What is Maestro?

Maestro is a local, chat-first orchestrator for software work. It does not replace the provider accounts or CLIs you choose. It coordinates them around a registered Git project, records the execution in SQLite, and keeps the final decision with a person.

The control loop

1. Register a Git project.
2. Create a task with the user’s original request preserved.
3. Prepare an isolated worktree and branch.
4. Start a persistent Goal that moves through planning, implementation, testing and review.
5. Run deterministic checks, create a commit, push the branch and open a draft pull request.
6. Review the evidence and decide what happens next on GitHub.

The Dashboard and CLI use the same local application contracts and database. Telegram is an optional control surface, not a requirement for the core runtime.

What Maestro is not

• It is not an AI provider, model host or billing account.
• It is not a hosted multi-tenant service; the normal runtime is local to the operator.
• It is not an unrestricted shell exposed through Chat. Chat actions are governed by access mode.
• It does not guarantee quota readings when a provider does not expose them.
• It does not merge a standalone pull request just because a Goal completed.

The important boundaries

Provider authentication stays with the provider CLI or API key. Git changes happen in a task worktree. Secrets and local paths are redacted from user-facing evidence. Human review remains the merge gate for the standalone flow.