Overture is BrandByX's GitHub Projects-focused fork of Symphony. It turns issue-backed GitHub Projects work into isolated, autonomous implementation runs using repo-owned workflows and per-issue workspaces.
This demo video shows the upstream Symphony orchestration model that Overture starts from. The current fork applies that model to GitHub Projects-backed work execution.
Warning
Overture is a low-key engineering preview fork for testing in trusted environments.
Overture works best in codebases that have adopted harness engineering. It is the next step after managing coding agents: managing the work that needs to get done.
Tell your favorite coding agent to build Overture in a programming language of your choice:
Implement Overture according to the following spec: https://github.com/BrandByX/overture/blob/main/SPEC.md
Check out elixir/README.md for instructions on how to set up your environment and run the Elixir-based Overture implementation. You can also ask your favorite coding agent to help with the setup:
Set up Overture for my repository based on https://github.com/BrandByX/overture/blob/main/elixir/README.md
Overture currently ships a GitHub Projects-backed Elixir implementation derived from the upstream Symphony codebase.
- Public-facing repo and documentation identity now use
Overture. - Internal runtime identifiers such as
SymphonyElixir,:symphony_elixir, and./bin/symphonyremain unchanged in v1. - GitHub Projects is the real production tracker contract in v1.
- Runnable tracker inputs are issue-backed project items only.
- PR-linked project items, draft items, and other non-issue project items are skipped by the runtime.
- The
upstreamremote should remain configured so future upstream changes can be reviewed and cherry-picked selectively.
AGENTS.mdARCHITECTURE.mddocs/README.mdOVERTURE_BASELINE.md
This project is licensed under the Apache License 2.0.