v0.6 Plugins ship to Railway · Vercel · EAS · GitHub

The vibe-coding IDE
that brings a team.

Symphony is a local-first desktop app that gives vibe coders a real dev team — a lead, a developer, a reviewer, a tester — so an idea can become a shipped, deployed app. On your AI subscription. In your git folder. On your machine.

Download for Windows → Watch the demo
✓Free & open source No API keys Your git, your code
symphony · new-project-plan · cockpit
4 / 5 runtimes

new-project-plan

running
✓Provisioned ✓Members joined 3Ready · 10 open 4Review
L
leadLead
working
▸Dispatching task T-003 to developer
D
developerDeveloper
coding
▸Wiring chore templates → instance service
R
reviewerReviewer
reading
▸Reading diff on points/ledger.ts
T
testerQA
queued
▸Spec test suite for offline outbox
TasksRuntimesFiles
10 open · 4 in flight
T-003
Offline-first local persistence & sync outbox
developer · writing…
T-004
Chore templates + instance generation service
lead ·spec drafted
T-007
Points ledger + wallet balance rules
reviewer ·reading diff
The demo

Three minutes,
one idea to a shipped app.

Watch a vibe coder describe a chore-and-allowance app in plain English, and the team take it from Foundry plan to deployed preview.

symphony·demo·v0.6.2
04:00
The gap

AI dev tools either talk down to you,
or hold your code hostage.

Symphony is for the people in between — real ideas, tech-adjacent skills, priced out of professional software, burned by both extremes.

Pro-dev camp

“I don't know what npm install means.”

Cursor and Claude Code assume you're already driving a code editor. Non-developers bounce off the terminal and the file tree before they ever get to the part they're good at.

— too steep
Symphony

Real code on your machine, with a soft on-ramp.

Foundry does the project scaffolding for you. A team of specialized agents handles the build. The output is an honest git repository in your home folder — yours, not ours.

— the work is the point
Cloud-sandbox camp

“Wait… where is my code?”

Bolt, base44, Replit Agent trap you in slop-cloud workspaces. The code is the platform's. Trying to take ownership is a hostage negotiation with an export button.

— no exit
How it works

From a sentence to a shipped slice
in four movements.

You describe what you want. Foundry plans it. The team builds it. You review. Nothing leaves your machine unless you push it.

01 / Describe
One paragraph, no jargon.

Tell Symphony what you want to build, in plain English. No templates, no checklists.

> an Android-first, offline-first family chore
  & allowance app with weekly payouts▍
02 / Foundry plans
Brief, spec, roadmap, tasks.

Foundry turns the idea into structured project docs you can read and edit before any code lands.

brief.md ● drafted
spec.md ● drafted
roadmap.md ● 6 slices
tasks/ ▸ 23 items
03 / The team builds
Lead, architect, dev, reviewer, QA.

Five role-specialized agents work in parallel from the roadmap. You watch, comment, or step away.

lead→ dispatch
architect→ data model
developer→ csv parser
tester→ e2e
04 / You ship
Real git, real code, your repo.

Commits land on a branch in your git folder. Push to GitHub, deploy, or do nothing.

a3f81c2  feat: chore instance gen
e2b4d10  test: payout computation
7c1e9aa  chore: bump zod
~/Project-TOAD/toad-local
The ensemble

One planner.
A team of four.

Foundry handles discovery and planning. Then the team — lead, developer, reviewer, tester — works the roadmap in parallel through your local Claude, Codex, or Gemini CLI.

F
Planner
Foundry

A planning chat that turns your idea into seven docs — brief, spec, roadmap, task breakdown, plus steering, design decisions, definition-of-done. Editable before any code lands.

briefspecroadmaptasks
L
Orchestrator
lead

Holds the roadmap in its head. Dispatches tasks, schedules reviews, decides when something’s ready to merge. The closest thing to a tech lead the team has.

dispatchschedulinghandoff
D
Developer
developer

Writes the code. Picks the libraries. Splits its work into hunks you can accept, edit, or reject one at a time inside Cockpit.

coderefactormigrate
R
Reviewer
reviewer

Reads every diff before it lands. Flags drift from the spec, missing tests, weird API choices, anything the developer got proud of.

diffspec-fitstyle
T
QA
tester

Writes and runs tests against each slice. Spins up the app, clicks the buttons, reports back what broke and where.

testse2erepro
Inside the app

Something is always
happening on the canvas.

The workspace shows every agent in real time — tasks moving, files changing, reviews landing, drift trending. No black box, no spinner of doom.

symphony-demo · Tasks · new-project-plan
4 / 5 runtimes opus 4.6

new-project-plan

10 total · 0 in flight · 0 in review
Kanban
List
Diff
Run
T-001 — Define MVP requirements & UX flows
lead
+148 −22
T-002 — Data model + backend scaffold (family tenant + invite)
developer
+312 −5
T-003 — Offline-first local persistence & sync outbox
developer
writing…
T-004 — Chore templates + instance generation service
reviewer
reading
T-005 — Kid experience: queue + submit
tester
queued
T-007 — Points ledger + wallet balance rules
lead
queued
Cockpit — watch the team work Foundry — discovery & planning chat Drift — spec-fit monitor (L1·L2·L3) Plugins — Railway · Vercel · EAS · GitHub
What you keep

Your subscription. Your code.
Your machine.

Symphony is built around the idea that the work belongs to you. No API keys to wrangle. No per-token surprise. No platform that quietly owns your repo.

Claude
Opus 4.6
GPT
5.4
Gemini
Pro
Your subscription.

Symphony talks to the official Claude, Codex, and Gemini CLIs on your behalf — using the session you already pay for. No keys, no per-token billing, no surprise invoice.

1commit a3f81c2 (HEAD → main)
2+ export function generateInstances(template) {…}
3+ // weekly cron, idempotent
4- // TODO: chore generation
5~/Project-TOAD/toad-local
Your code.

The output is a real git repository in your home folder. You can push to GitHub, hand it to a developer, fork it, delete it — it's just code, on disk, owned by you.

♪
⌀
no cloud
Your machine.

The whole thing runs locally. Agents read and write files on disk. Nothing leaves your laptop unless you push it. Works the same on a plane, in a café, or off the grid.

How it compares

Not a code editor.
Not a sandbox. A studio.

A quick read on where Symphony sits relative to the tools you might be comparing it to.

Symphony local studio Pro-dev IDEs cursor / claude code Cloud agents bolt / base44 / replit
Plans the project for you Foundry, with editable docs You drive Sort of — opaque
Multiple agents in parallel 5 roles, live canvas One conversation One agent
Uses your existing AI plan Claude Pro · GPT Plus · Gemini API keys, per-token Their subscription on top
Code lives on your machine Real git folder in $HOME Your workspace Their cloud
Soft on-ramp for non-devs Welcome banner, no wizard Terminal-first Friendly, but…
You own the output Plain git, no lock-in Yes Export, maybe
What's shipping

We work in public.
Here's the score so far.

Symphony is built in slices, in the open. The same roadmap Foundry produces for your projects, we keep for our own.

Shipped · v0.6
Foundation
  • First-run lands new users in Foundry with a welcome banner
  • Foundry plans with Claude or Codex CLI (F.2)
  • Lead / Developer / Reviewer / Tester team loop
  • Drift Monitor — spec-fit scoring & remediation
● In flight
Maintenance mode
  • Reopen projects without re-running discovery
  • Hunk-level diff accept / reject
  • Persist agent state across sessions
Developer mode
  • Inline terminal, scoped to the project
  • Raw event log for power users
  • Drive agents directly from the canvas
Exploring
Ensemble
  • Custom agent roles (designer, data, etc.)
  • Run alongside a teammate's repo
  • Windows / Linux builds
Common questions

A few things people ask
before downloading.

Do I need to know how to code?
No. Symphony is designed for people with real ideas and tech-adjacent skills, not professional engineers. You describe what you want; Foundry handles the planning; the team handles the building. As you grow, you can flip on Developer mode and drive more directly.
How does it use my Claude / ChatGPT / Gemini subscription?
Symphony talks to the official Claude, Codex, and Gemini CLIs on your behalf, using the session you already pay for. No API keys, no per-token bills — you use the same allowance you'd use chatting with the assistant directly. The Providers settings panel shows live signed-in status and remaining plan quota.
Where does my code live?
In a normal git folder on your machine — by default under ~/Projects/<your-project>. You can cd into it, push it to GitHub, open it in any editor, or delete it. Symphony never touches your files outside that folder.
What's Drift Monitor?
A continuous spec-fit check the team runs against the roadmap. It scores Architecture, Checklist, Slice Scope, Test Truth, and Risk. If the build starts wandering from the brief, Drift catches it and proposes a correction task.
Is it really local-first?
The app itself runs locally. The agents reach out to the AI providers you've authorized — that's the only network traffic. No telemetry on your code, no shared workspaces, no servers holding state for you.
Is it open source?
Yes — Apache 2.0. The orchestration engine, the agent definitions, and the desktop shell are all on GitHub. Forks and self-hosted deployments are welcome and unblocked.
What operating systems are supported?
Windows today (Tauri-based desktop shell). macOS is in beta for sponsors; Linux is on the roadmap once maintenance mode lands. The orchestrator itself is cross-platform Node — anywhere Claude / Codex / Gemini CLI run, Symphony can run.
Download · v0.6.2 · Windows (macOS in beta)

Stop describing software.
Start shipping it.

Free, open source, and runs against the AI subscriptions you already have. Your first project is usually live in an afternoon.

Download for Windows → ★ Star on GitHub