One GitHub Issue, from code to PR -- autonomous Claude Code orchestration.

Symphony-CC turns GitHub Issues into Pull Requests -- autonomously. It polls your repository for labeled issues, spins up isolated git worktrees, runs Claude Code in non-interactive --print mode, and opens PRs with the results. A finite state machine (FSM) tracks each task through its lifecycle: QUEUED -> PREPARING -> RUNNING -> SUCCEEDED / PR_CREATED, with automatic retries on failure (up to 3 attempts) before escalating. Post an issue, label it, and walk away.

• Unattended autonomous execution -- Label an issue and leave. Symphony handles the rest.
• Parallel processing -- Run up to 2 tasks concurrently, each in its own git worktree.
• Automatic retry + escalation -- Failed tasks retry up to 3 times, then escalate with full logs.
• Rich TUI dashboard -- Real-time view of queues, active tasks, and completion status.
• GitHub comments + Slack notifications -- Get notified on success, failure, or escalation.
• Per-issue budget cap -- Default $5 USD limit per task to prevent runaway costs.
• Frontmatter optional -- Issues work with or without YAML frontmatter.
• /symphony slash command -- Integrate directly into your Claude Code workflow.

• Python 3.12+
• Claude Code CLI installed and authenticated
• GitHub CLI (gh) installed and authenticated
• Git 2.15+ (worktree support)

git clone https://github.com/qjc-office/symphony-cc.git
cd symphony-cc
pip install -e .

1. Initialize your project:

cd your-project
symphonyctl init --repo owner/repo --budget 5

This creates a config.yaml with sensible defaults. Use --non-interactive for CI environments.

2. Create a GitHub Issue with the trigger label:

Add the symphony:ready label to any issue. Optionally include YAML frontmatter:

---
mode: feature
max_iterations: 10
budget_usd: 3
---

## Task

Add input validation to the /api/users endpoint using zod schemas.

## Acceptance Criteria

- All request bodies validated with zod
- Error responses follow RFC 7807 format
- Tests cover valid and invalid inputs

3. Start Symphony:

# Foreground (see logs in real-time)
symphonyctl start --foreground

# Background daemon
symphonyctl start

# Or jump straight to the dashboard
symphonyctl dashboard

Symphony picks up the issue, creates a worktree, runs Claude Code, and opens a PR.

QUEUED ──> PREPARING ──> RUNNING ──> SUCCEEDED ──> PR_CREATED
              |             |             |
              |             v             |
              |          FAILED ──> RETRYING ──> (back to PREPARING)
              |                         |
              |                         v (max retries exceeded)
              |                     ESCALATED
              v
           FAILED (workspace setup error)

Symphony is configured via config.yaml at your project root. Every option can be overridden with environment variables.

tracker:
  kind: github
  repo: owner/repo
  trigger_label: "symphony:ready"
  active_labels: ["symphony:in-progress"]
  terminal_labels: ["symphony:done", "symphony:failed"]

polling:
  interval_s: 30

workspace:
  root: ~/symphony-workspaces

agent:
  max_concurrent: 2
  max_retries: 3
  retry_delay_s: 60
  max_budget_usd: 5
  model: opus
  allowed_tools: "Bash(*),Read(*),Write(*),Edit(*),Glob(*),Grep(*)"
  default_mode: feature
  default_max_iterations: 10

hooks:
  after_create: ""
  before_run: ""
  after_run: ""

notifier:
  github_comment: true
  slack_webhook_url: ""
  events: [succeeded, failed, escalated]

Environment variables always take precedence over config.yaml values.

Enabled by default. Symphony posts status updates directly on the issue:

• On success: Summary of changes + link to the PR
• On failure: Error logs and retry count
• On escalation: Full diagnostic info for human review

Configure notifier.slack_webhook_url in config.yaml or set SYMPHONY_NOTIFIER_SLACK_WEBHOOK:

notifier:
  slack_webhook_url: "https://hooks.slack.com/services/T00/B00/xxx"
  events: [succeeded, failed, escalated]

Contributions are welcome! Please see CONTRIBUTING.md for guidelines.

# Run tests
pytest

# Run tests with coverage
pytest --cov=lib

MIT