Eight musicians gathered around a workbench on a theater stage — the architect in a burgundy vest holds a gold baton pointing at blueprints while musicians with diverse instruments look on, one carries a stack of sheet music, one sets up drums off to the side

Every agent knows its part.

Spec-driven coordination for AI-assisted development.

Define work as specs. Run it anywhere — locally, or on Synchestra Hub.

AI agents are powerful. Coordinating them is a different problem.

Running one agent on one task works. Running five agents across three platforms on a tree of interdependent tasks? That's where things fall apart.

💸

Context is expensive

Every time an agent starts, it needs to understand what's going on. Loading the full project context burns tokens and loses focus.

🗂️

State is scattered

What's been done? What's left? What's blocked? The answers live in chat logs, git history, and your head.

🔗

Agents can't find each other's work

Agent A finishes a sub-task. Agent B needs the output. Without a shared protocol, you're the glue.

👁️

Humans can't see what's happening

Agents work across platforms asynchronously. There's no dashboard, no progress bar, no single place to look.

One repo. One source of truth. No server needed.

When five agents work across three platforms, the answers to "what's done?" and "what's next?" need to live somewhere every tool can reach. Synchestra turns a git repository into a coordination protocol. The repo is the database. Git history is the audit trail.

🌳

Hierarchical

Features have sub-features. Tasks have sub-tasks. The directory tree mirrors how work actually decomposes.

🔀

Multi-platform

Claude Code, Cursor, GPT, custom scripts — any agent that can read files can participate.

Token-efficient

Auto-generates minimal per-task context. Agents stay focused, costs stay low.

🔒

Conflict-safe

Agents claim tasks atomically through git. Optimistic locking, schema-validated at every commit.

Three steps. No infrastructure.

1

Point it at your repo

Install the CLI to work locally, or connect via the web to manage projects across machines. A specscore-spec-repo.yaml links everything together.

2

Queue tasks

Create tasks from specs, plans, or freeform descriptions. Agents discover and claim them asynchronously using optimistic locking through git.

3

Monitor progress

Every task has a status. Every agent has a log. Watch work unfold in real time across platforms and agents.

Specs first. Then agents.

Synchestra doesn't replace your agent runtime. It's the layer above — defining what needs doing so agents can focus on how.

📐

Built on SpecScore

The specification format is SpecScore — an open-source framework for writing specs that AI agents can understand and execute. Features, plans, architecture, project structure — SpecScore defines the format. Synchestra adds orchestration, tasks, and coordination on top.

Use SpecScore standalone with any tooling you already have — or pair it with Synchestra for the full spec-to-execution workflow.

Traditional orchestrators Synchestra
State storageDatabase / API serverGit repository
Agent integrationSDK / API clientCLI, MCP, or direct file access
InfrastructureServer, database, networkingGit + single binary
Context loadingFull project dumpAuto-generated minimal context per task
Multi-platformLocked to one runtimeAny tool that can read/write files
CoordinationReal-time messagingAsync via repo state
Audit trailEvent log in databaseGit history
ValidationApplication-level checksSchema-enforced at commit time

vs agent frameworks

Agent frameworks are runtimes — they execute agents and chain tool calls. Synchestra is the coordination layer above. Your agents across any platform coordinate through the same repo.

vs project management

Linear, Jira — those track work for humans. Synchestra tracks work for agents and humans. Machine-navigable and human-readable.

vs CI/CD

CI/CD pipelines are linear and event-driven. Synchestra workflows are hierarchical and async. Tasks spawn sub-tasks dynamically.

You're going to ask these anyway.

"Isn't this just a well-organized repo?"

You could do what Synchestra does manually — like you could deploy without CI/CD or track bugs without an issue tracker. Synchestra is the automation and discipline layer that makes it sustainable. Schema validation, context generation, conflict resolution, progress tracking — the chain of small steps nobody has time to do consistently.

"Naming conventions are fragile. What happens when they break?"

They don't break silently. The CLI validates on every operation, pre-commit hooks catch problems before they enter the repo, pre-push hooks catch anything that slipped through, and GitHub Actions provide a final safety net.

"How does async coordination work without conflicts?"

Through optimistic locking — the same mechanism distributed systems have used for decades. Agents claim tasks by committing and pushing. If the push fails, someone else got there first. For the remaining edge cases, Synchestra provides AI-powered merge resolution. The "commit often" philosophy minimizes the conflict window in the first place.

"Does this scale beyond a solo developer?"

Git already handles distributed collaboration. Schema validation works regardless of team size. Optimistic locking handles concurrency without a central coordinator. The same conventions that keep a solo developer organized keep a team aligned.

Synchestra builds Synchestra.

The best test of coordination infrastructure is using it yourself. Synchestra's own development — across three repos, multiple agents, and daily commits — is managed by Synchestra. The codebase is small by design — every rough edge felt immediately, fixed quickly, and built in the open.

Install the CLI

One command. Detects your OS and architecture, downloads the latest release, verifies the checksum, and installs the binary.

macOS / Linux
curl -fsSL https://synchestra.io/get-cli | sh

Platforms

Linux and macOS, amd64 and arm64. Windows archives available from releases.

Verified

SHA-256 checksums are downloaded and verified automatically before installation.

No dependencies

Single static binary. No runtime, no package manager, no containers.

Synchestra Hub

You run everything locally with your agent of choice. And you probably should — it's fast, it's private, it works.

But then you need to close your laptop. The agent isn't done. You wish it could keep going without you, but it can't. The work stops when you stop.

Synchestra Hub picks up where your laptop leaves off.

Run agents locally, on a remote VM, or in the cloud. Transfer work and context mid-flight. Come back to finished tasks, not stale sessions.

Remote execution

Dispatch agents to VMs or cloud infrastructure. Self-hosted or managed — your choice.

Dashboard & visibility

See what every agent is doing across every project. Task progress, logs, and status — all in one place.

API & integrations

Queue tasks, trigger workflows, and connect to your existing tools through the Hub API.

Synchestra Hub builds on the same specs and CLI you already use. No lock-in — the open-source foundation works independently.

Ready to orchestrate?

Get started in minutes. No infrastructure required.

Explore the source code & specifications →