Skip to content

Contributing

Start with the Maestro repository, read its CONTRIBUTING.md, and search existing issues before opening a new one.

  • Explain the user-visible behavior and the safety boundary affected.
  • Add or update tests for state transitions, provider behavior and UI/API parity.
  • Run typechecks, tests and the relevant build locally.
  • Do not include .env.local, OAuth artifacts, provider tokens, .maestro/, logs or machine-specific paths.
  • Keep documentation claims tied to the current main implementation; label future work as future.

The runtime is MIT-licensed. The repository’s Code of Conduct and Security policy apply to contributors.