Providers

Maestro routes capabilities to provider adapters. A provider can be an authenticated CLI, an API-key-backed endpoint, a local model runtime or a custom CLI configuration.

Built-in presets

The source distribution currently includes presets for:

• Claude Code (claude), usually authenticated with a Claude account or API-backed CLI.
• Codex (codex), authenticated through the Codex CLI account flow.
• Gemini Antigravity (agy), using the local Google subscription session.
• GitHub Copilot CLI (copilot).
• OpenCode/API presets, including OpenAI-compatible, OpenRouter, Gemini API and DeepSeek.
• Ollama for local models.

The exact available model list and authentication state depend on the machine. Installed does not mean authenticated, and authenticated does not mean healthy or available for every capability.

Connect and rescan

Use Providers in the Dashboard to install instructions, authenticate and rescan. Rescanning invalidates discovery/health caches without restarting Maestro. Provider account data remains owned by the provider CLI; API keys are stored through the local configuration path and must not be committed.

Antigravity needs both the agy CLI and its local signed-in session. A terminal that can launch agy is necessary but does not prove that an RPC quota session is available.

Control modes

Each provider can be enabled, paused or disabled. Fallback can be enabled or disabled, and the control plane can require a preferred provider for a capability. Changes apply to the next provider lease; a running step is not silently swapped halfway through.

Routing boundary

With automatic fallback enabled, Maestro follows the configured capability order and then its defaults. Required, paused, unhealthy or unavailable providers are not silently substituted when policy requires a specific provider. A provider failure is recorded with a category and may place the Goal in waiting_provider.