Symphony-ts ports OpenAI Symphony to TypeScript

Less a language port than a portability play: if Symphony’s workflow is the real innovation, moving it into TypeScript could matter more than sticking with the original Elixir stack. The main question is whether this stays close enough to upstream Symphony to be a useful mirror, or evolves into its own agent-orchestration dialect.

• –It lowers the barrier for teams already living in Node, TypeScript, and Codex tooling.
• –The repo keeps the core Symphony idea intact: tracker-driven issue intake, isolated workspaces, retries, cleanup, and a live dashboard.
• –The setup is still opinionated and trust-heavy, which makes it feel aimed at serious internal automation rather than casual agent demos.
• –Because it is unofficial, compatibility with future Symphony changes is the biggest long-term risk.