Full-stack features live in more than one repo. Sinfonie gives every feature its own isolated workspace: a worktree on the same branch in every repository you pick, side by side, with a crew of models working across them.
Implement ACME-142: apply the new checkout discount rules per customer tier. Backend in api, UI in web. 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 discount rules are resolved in both repos
implementersonnet-5web: show the tier discount at checkout
testerhaiku-4-5pnpm test --filter 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
Isolated workspaces, every repo a feature touches.
Worktrees, chat, diffs, terminals, files, a browser and a database viewer, all per workspace. Spaces to keep clients apart, a crew of models and a lean mode to keep tokens down, a review cockpit for the pull requests waiting on you, and an on-call agent that triages Slack alerts and drafts the fix.
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, or Codex, Gemini and Grok as crew members. Every delegation is visible, with its model, steps and cost.
Review cockpit
Every open PR of a space. Run an AI review with code snippets per finding, post one GitHub review with inline comments and a verdict, then let the agent fix the findings and iterate until the PR is ready.
Spaces
Personal, work, client: each space owns its repos, Jira, accounts and defaults.
Jira, Linear, Slack, Google Cloud, MCP
Start a workspace from a ticket and get a branch name for free. Sign in once per space and the agents get the tools: Jira and Linear issues, Slack channels, read-only Cloud Logging, Cloud Run and Error Reporting, plus any MCP server.
Setup assistant
Tell it how your team builds, tests and ships. It interviews you, proposes a crew with prompts written for your repos, adds repositories, creates spaces, connects integrations and sets cost modes. Every change is confirmed first.
Database viewer
Postgres, MySQL, SQLite, MongoDB and BigQuery, directly, through SSH, or through Cloud SQL with your Google login. Schema tree, SQL editor, ERD, inline editing, CSV import and export. Read-only by default, for you and for the agents.
On-call agent
Watches your Slack alert and support channels, triages each incident against your code and your Cloud Logging, Cloud Run and Error Reporting, proposes replies you approve, and opens a draft PR with the fix when it is sure of the cause.
Usage and lean mode
See your subscription windows and where the tokens went. A preflight card warns before a task that will not fit. Budget and lean modes run one Sonnet agent with trimmed tools and capped turns, per workspace, space or app.
Browser and files
An embedded browser the agent can drive: check localhost, read docs, operate consoles you are signed into, with sensitive sites always asking first. A files tab shows every worktree with git status.
Scriptable workspaces
A sinfonie.json per repo runs your setup, dev server and cleanup with a dedicated port block per workspace. 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.
01
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.
Acme
├─ web
├─ api
└─ jira · github · analytics-mcp
02
New workspace
Pick the ticket. Sinfonie cuts a branch in every repo, creates the worktrees, runs each repo's setup script.
~/sinfonie/workspaces/acme-142-checkout/
├─ web ⎇ acme-142-checkout
└─ api ⎇ acme-142-checkout
03
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 #412 web ✓ checks
PR #388 api ✓ checks
Jira ACME-142 → 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
sinfonie.json · one per repository
// per repository, picked up automatically
{
"scripts": {
"setup": "pnpm install",
"run": "pnpm dev --port $SINFONIE_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 "acme-142-checkout" spans 2 repositories.
- web: ~/sinfonie/workspaces/acme-142-checkout/web
- api: ~/sinfonie/workspaces/acme-142-checkout/api
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.
How do updates work?
The app is signed and notarized with Apple. New releases download in the background; when one is ready the sidebar offers Restart now, Restart when idle (once no agent is running and you have stepped away) or On next quit. Nothing installs behind your back.
macOS says it "could not verify Sinfonie is free of malware". What now?
The beta is not yet notarized with Apple, so macOS blocks the first launch. Click Done (not Move to Trash), then open System Settings → Privacy & Security, scroll to the Security section, and click Open Anyway next to Sinfonie. Confirm once with your password and it opens normally from then on. Terminal alternative:
This only happens with builds older than 0.1.3; current downloads are notarized and open normally.
Does it work with a single repository?
Yes. A workspace can hold one repo or five. The multi-repo model only matters when a feature spans several; everything else, worktrees, chat, diffs, terminals, review, is the same either way.
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?
Yes. Codex, Gemini CLI and Grok run as engines or as crew members with their own logins, and API providers plug into the native engine. The orchestrator sees them as tools and every delegation stays visible.
Can the agents touch my database?
Only what you allow. Every connection is read-only by default: statements are classified and run inside a read-only transaction with a timeout and a row cap, and agents get the same rules. A connection can allow writes, in which case you confirm each statement, and the on-call agent never writes. Passwords stay in the macOS keychain; Cloud SQL uses your own Google login.
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.
One workspace per feature. Every repo it touches.
One workspace per feature, every repo it touches, a crew that knows the difference between exploring and deciding.
