Symphony-style unattended issue orchestration for the Pi coding agent using Linear.
Agent: Functional — the core orchestration loop, PR automation, and merge execution are implemented. Not yet running in production.
Translation: This will let you give in to vibeslop agentically engineer at a new level of abstraction.
- Polls a Linear board for eligible issues
- Creates an isolated workspace per issue
- Launches a Pi coding worker in RPC mode
- Lets the worker implement autonomously within repo-defined policy
- Manages the full PR lifecycle: create/reuse PRs, self-review, merge execution
- Captures proof-of-work artifacts and surfaces status through a dashboard and JSON API
- Writes local-first
symphony_runanalytics extracts for worker attempts under the run logs root - Retries, reconciles, and recovers safely
- Orchestrator (Elixir/OTP) — long-running daemon adapted from OpenAI Symphony
- Worker extensions (TypeScript) —
workspace-guard,proof,linear-graphql - Workflow contract — repo-owned
WORKFLOW.mdwith policy-driven prompt templates
make setup
make checkSee docs/DEV.md for the full developer workflow.
pi-symphony/
orchestrator/elixir/ # Elixir/OTP orchestrator (adapted from OpenAI Symphony)
extensions/ # Pi worker extensions
examples/ # fixtures and sample workflows
docs/ # architecture, developer docs, contracts
docs/archive/ # historical migration notes
docs/PLAN.md— implementation plan and architecturedocs/DEV.md— local development workflow and quality bardocs/PI_RPC_CONTRACT.md— Pi worker runtime contractdocs/ORCHESTRATED_PR_FLOW.md— PR automation designdocs/PR_AUTOMATION_SCHEMA_PROPOSAL.md— config and runtime contract for PR automationdocs/WORKFLOW_PR_AUTOMATION_DRAFT.md— booking-demo workflow draftTHIRD_PARTY_NOTICES.md— vendored code attribution
MIT for original project code. Vendored third-party code retains its upstream license; see THIRD_PARTY_NOTICES.md.