Contribute to open source projects by donating AI tokens through Maestro Symphony.
Maestro Symphony is a community-driven program that connects Maestro users with open source repository maintainers seeking contributions. Think of it like distributed computing for AI-assisted development — instead of donating CPU cycles, users donate LLM tokens to advance open source.
Before starting a Symphony contribution, ensure you have:
GitHub CLI required. Symphony uses the GitHub CLI (gh) to create draft PRs, manage contributions, and claim issues. Install it and run gh auth login to authenticate. Symphony will verify this before allowing you to proceed.
Build tools required. Symphony clones repositories and runs Auto Run documents that may compile code, run tests, and make changes. Make sure you have the project’s build tools and dependencies installed (e.g., Node.js, Python, Rust toolchain). Consider cloning the project first and verifying you can build it successfully — without the right toolchain, the contribution will likely fail.
Issues with the blocking label appear in a separate “Blocked” section, grayed out with a lock icon. These represent work that has unmet prerequisites — the repository maintainer will remove the blocking label once dependencies are satisfied. Blocked issues cannot be started but are shown so contributors can see the full scope of planned work.
Review completed contributions with aggregate stats at a glance:The header shows your totals: PRs created, merged count, tasks completed, tokens used, and dollar value donated. Each contribution card displays:
Symphony sessions appear in the Left Bar like any other session:
Named “Symphony: owner/repo #123”
Optionally grouped under a “Symphony” group
Full access to AI Terminal, Command Terminal, and Auto Run controls
You can interact with Symphony sessions just like regular sessions — pause Auto Run, make manual edits, or switch to the Command Terminal for custom commands.
Repository owners create issues with the runmaestro.ai label:
Copy
## Add unit tests for auth moduleWe need comprehensive test coverage for the authentication module.### Auto Run Documents- `docs/symphony/auth-tests-1.md`- `docs/symphony/auth-tests-2.md`- `docs/symphony/auth-tests-3.md`### ContextThe auth module is at `src/auth/index.ts`. Tests should use Jest.
Each document path should point to an Auto Run-compatible markdown file with task checkboxes.
Symphony uses deferred PR creation to avoid GitHub’s “no commits between branches” error. When you start a contribution, Maestro sets up the branch and documents but waits until the first commit to create the draft PR:
Start contribution → Branch created locally, Auto Run begins processing
First commit → Draft PR automatically created, claims the issue
Subsequent commits → Push to the same PR
This means issues show as “in progress” once the first commit lands. The claiming mechanism:
No draft PR → Task is available
Draft PR exists → Task is in progress (first to commit wins)