Security
Maestro runs local automation around code and provider credentials, so the boundaries matter.
Defaults
Section titled “Defaults”- The Dashboard binds to loopback by default.
- Provider tokens, OAuth codes and Telegram tokens stay out of Git and user-facing evidence.
- Git work is scoped to registered repositories and prepared worktrees.
- Provider output is untrusted until validation and review pass.
- Chat mutations go through explicit access modes and governed application actions.
- Standalone pull-request merge remains a human decision.
Operator responsibilities
Section titled “Operator responsibilities”Install provider CLIs from official sources, review their login/permission prompts, keep GitHub authentication scoped to the account you intend to use, and do not expose the local API port to an untrusted network. Keep the execution root out of OneDrive or other sync tools when possible.
Reporting
Section titled “Reporting”Do not publish credentials, private paths, database files or exploit details in an issue. Follow the security policy in the Maestro repository for a private report.