macOS · Apple Silicon · v0.1.0

One workspace across all your repositories.

Full-stack features live in two repos. Sinfonie runs Claude Code in isolated workspaces like Conductor does, with the difference that matters: a workspace is a worktree on the same branch in every repo you pick, and a crew of models works across them.

Download for Mac See how it works Free while in beta · unsigned build, right-click → Open

Sinfonie — Lumepic / enhanced-packages

enhanced-packagesIn progressfrontend-monorepobackend-servicesPR #7932 · 2 threads

Implement SD-3825: assign the enhanced-packages arm per buyer via PostHog. Backend in backend-services, UI in frontend-monorepo. Explore, implement both sides, run the tests, review before you report back.

Splitting this across the crew. Two independent delegations first.

explorerhaiku-4-5Find where package arms are resolved in both repos

implementersonnet-5backend-services: PostHog flag evaluation for buyer arm

implementersonnet-5frontend-monorepo: read arm from purchase payload

testerhaiku-4-5pnpm test --filter spotted-api · 212 passeddone

revieweropus-5Diff review: 2 findings, safe to commit after fixing the nil guarddone

orchestrator opus-5

Built for the way you actually work

Everything Conductor does. Then the part it doesn't.

Isolated worktrees, chat, diffs, terminals and run scripts, all per workspace. Plus the multi-repo model, spaces, a crew of models and a review cockpit.

Multi-repo workspaces

One name, one branch, a worktree in each repo, side by side in one folder. Created, run and archived together, with a warning if anything is uncommitted or unpushed.

A crew of models

The chat model orchestrates. An explorer on Haiku, implementers on Sonnet, a reviewer on Opus. Every delegation is visible, with its model, steps and cost.

Review cockpit

Every PR waiting on you, per space. Run an AI review, approve findings one by one or all at once, post a single GitHub review with inline comments and a verdict.

Spaces

Personal, Lumepic, Howdy: each space owns its repos, Jira, GitHub orgs, MCP servers, Claude account and model defaults. Switch with a swipe, like Arc.

Jira, GitHub, MCP

Start a workspace from a ticket and get a branch name for free. PR status and review threads per repo. Log in to Jira once and Claude gets the Atlassian tools.

`conductor.json` compatible

Your setup, run and archive scripts work unchanged, ports included. Fork, resume and queue messages like the CLI. Errors show in the chat, never silently.

Three steps

From ticket to two pull requests.

The workspace is the unit of work. Everything else follows from it.

Add repos to a space

Point Sinfonie at your frontend and backend. Pick the Claude account, Jira site and MCP servers the space should use.

Lumepic ├─ frontend-monorepo ├─ backend-services └─ jira · github · posthog-mcp

New workspace

Pick the ticket. Sinfonie cuts a branch in every repo, creates the worktrees, runs each repo's setup script.

~/sinfonie/workspaces/sd-3825-posthog-arm/ ├─ frontend-monorepo ⎇ sd-3825-posthog-arm └─ backend-services ⎇ sd-3825-posthog-arm

Ship

Talk to the orchestrator. It fans out to the crew, you watch every delegation live, then open both PRs from the app, linked to each other and to the ticket.

PR #7932 frontend-monorepo ✓ checks PR #1041 backend-services ✓ checks Jira SD-3825 → In review

Cost where it counts

Frontier model for judgment. Cheaper models for the rest.

Reading twenty files to answer "where is this used" costs a tenth on Haiku of what it costs on Opus. Sinfonie ships a default crew and lets you edit every member per space.

Agent	Model	Does
orchestrator the chat	opus · fable	Plans, delegates, integrates, talks to you
explorer read-only	haiku	Finds code, traces call sites, answers "where"
implementer	sonnet	A well-specified change inside one repo
tester shell only	haiku	Runs tests and type-checks, reports failures
reviewer read-only	opus	Reviews the diff before commit, by severity

conductor.json · works as-is

// per repository, picked up automatically
{
  "scripts": {
    "setup":   "pnpm install",
    "run":     "pnpm dev --port $CONDUCTOR_PORT",
    "archive": "./scripts/cleanup.sh"
  },
  "runScriptMode": "concurrent"
}

Each workspace gets a block of ten ports. Two full-stack workspaces running side by side never collide.

what the orchestrator sees

Workspace "sd-3825-posthog-arm" spans 2 repositories.
- frontend-monorepo: ~/sinfonie/workspaces/…/frontend-monorepo
- backend-services:  ~/sinfonie/workspaces/…/backend-services
Crew: explorer (haiku) · implementer (sonnet)
      tester (haiku) · reviewer (opus)
Delegate exploration and tests. Keep judgment.
Never let two agents edit the same repo at once.

Questions

Straight answers.

Do I need an API key?

No. Sinfonie runs Claude Code through the official Agent SDK with your existing Claude login. If you use Claude Code today, you're set. You can add more accounts and pick one per space.

Why is the download unsigned?

Sinfonie is in beta and not yet notarized with Apple. On first launch, right-click the app and choose Open, or allow it under System Settings → Privacy & Security. The app checks for new versions itself and shows a download banner.

Does it replace Conductor?

For single-repo work they're equivalent: worktrees, chat, diffs, terminals, conductor.json. Sinfonie is for the moment a feature needs a worktree in more than one repository, and for running a crew of models rather than one.

Where does my data live?

On your Mac. Workspaces are plain git worktrees in a folder you choose. Chats, settings and tokens stay in your user library; Jira tokens are encrypted with the system keychain. Nothing is sent anywhere except to the services you connect.

Can I use models from other providers?

Today the crew is Claude models at different tiers. External workers such as Codex or Gemini CLI as crew members are next on the roadmap, exposed as tools the orchestrator can call inside a worktree.

Shape it

Tell me what you need.

Sinfonie is in beta and built from user requests. Feature ideas, bugs, rough edges: everything lands in one queue that decides what ships next. You can also send feedback from inside the app.

Stop juggling two Conductor windows.

One workspace per feature, every repo it touches, a crew that knows the difference between exploring and deciding.

Download Sinfonie

macOS 13+ · Apple Silicon · needs git and a Claude Code login