OpenSymphony
EN ES ZH PT

A control plane for orchestrating agent work from specs to execution.

OpenSymphony brings issue tracking, isolated workspaces, execution, review, and recovery into one supervised loop. It implements the Symphony model with Rust orchestration, Linear as the work source, and OpenHands as an independent execution harness that keeps provider and model choices flexible while orchestration stays stable.

GitHub repo Documentation DeepWiki
Local-first MVP Issue-scoped workspaces Linear + OpenHands Review inside the loop
OpenSymphony Control surface

Tracker

The issue becomes the control surface.

Work starts in Linear and stays attached to the work item.

Runtime

Execution stays isolated and inspectable.

Each issue gets its own workspace, run history, and recovery path so long-running work stays legible.

Policy

Repository rules become executable workflow.

WORKFLOW.md, AGENTS.md, and local skills shape how the system runs, reviews, and recovers.

OpenSymphony TUI showing issue orchestration state.
Linear board with issues managed through the OpenSymphony workflow.

Why it matters

Long-horizon agent work needs a work system around the agent.

OpenSymphony is for teams that want more than a prompt-and-pray loop. It keeps planning, execution, review, and recovery visible enough to supervise.

01

Durable state beats giant transcripts.

Workspaces, issue history, and control-plane snapshots make progress inspectable after the current session ends.

02

Rework stays in the same loop.

Review feedback, retries, and continuation guidance stay inside the same workflow.

03

Human judgment stays where it matters.

The operator moves up from prompt babysitting to workflow supervision, review, and policy changes.

Workflow

From spec to structured work.

OpenSymphony is opinionated about the loop: issues as the control surface, workspaces as the execution boundary, and workflow policy as the governing contract.

Workflow definitions shape the workspace layout and the manifests that persist issue state, conversation state, and run attempts.
Diagram showing workflow definitions feeding issue workspaces and persisted manifests across filesystem and code entity spaces.

01

Poll and select work

The orchestrator reads Linear, applies issue hierarchy rules, and chooses what is eligible to run.

02

Create or reuse the workspace

Each issue gets a deterministic directory with manifests, hooks, prompts, and generated context artifacts.

03

Dispatch through OpenHands

OpenHands handles the coding session while OpenSymphony keeps orchestration authority outside the harness.

04

Review, reconcile, and recover

The control plane, TUI, and issue trail keep retries, supervision, and restart recovery understandable.

Start here

Use the website as the fast orientation layer, then step into the repo, docs, DeepWiki, and template to work through the system in detail.

Code

GitHub repository

The implementation repo, README, architecture docs, and command surface.

Open resource
Docs

Documentation

Architecture, runtime, deployment, workspace lifecycle, and operations notes.

Open resource
Reference

DeepWiki

Structured walkthroughs of the codebase, components, and subsystem pages.

Open resource
Starter

Template repo

Bootstrap a greenfield project with workflow files, skills, and review automation.

Open resource
Video

Launch video

Short product tour for the release. The public link is still being wired in.

Latest updates

Build notes from the MVP

Read updates

April 9, 2026

Launching OpenSymphony

OpenSymphony launches as a local-first Rust implementation of the Symphony model for supervised long-horizon agent work.