Agents
In Maestro terminology, an agent is a provider adapter capable of executing one or more capabilities. Claude Code, Codex, Antigravity and custom adapters all implement the same execution contract: health, execution, optional model discovery and normalized outcomes.
Registry and leases
Section titled “Registry and leases”The AgentRegistry is the source of truth for provider health, capacity, active work and cooldowns.
A Goal acquires a lease before invoking a provider and releases it with feedback. This prevents two
writers from using a provider beyond its configured capacity and records retry/cooldown hints.
Normalized outcomes
Section titled “Normalized outcomes”Provider output is normalized into completed, changes requested, blocked, failed or cancelled, with retryability, failure category, duration, optional token usage and artifact references. Raw output is bounded and sanitized before it becomes user-facing evidence.
Adding a provider
Section titled “Adding a provider”Use the custom provider configuration path for a CLI, endpoint or local runtime. Define the command, arguments, capabilities, connection mode, model discovery and documentation URL. Treat provider output as untrusted and add tests before making a custom adapter a default route.