Harmony

A local-first operator system for AI-agent fleets. Design, ship, and maintain code with a team of llm agnostic agents trained to meet your own standards and best practices. Don't let velocity be a blocker.

Harmony pairs Fleet, a Go control plane that runs and records agent work, with Operator Cockpit, an desktop app that grows substrate -- all of your projects, tickets, docs, notes, decisions -- into easy to navigate dependency acyclic graph UIs rendered on a rich interactive canvas co-driven by ai chat. It surfaces what to do next and why by integrating live agent fleet usage with your workflow management control plane and optimizing your workflow to unblock as many coworkers, projects, or agents as possible. All work stays reviewable, controllable, and easier to improve on in a single place.

<sub>Operator Cockpit: inspect the DAG, workers, graph context, review packet, preview action, and ledger.


Fleet under the hood: run the control plane, proof loop, worker handoff, and audit trail.</sub>

The public repo is credential-free and fixture-safe. Demo Lab is fictional, but the product pattern is grounded in 900+ private fleet runs: see the fleet, decide what happens next, and turn the ledger into a better next run.

The Loop

AI-agent work gets hard to trust when the truth is scattered across chat threads, issues, pull requests, logs, local databases, and half-remembered decisions. Harmony turns that scattered work into one loop:

1. Plan the graph. Linear and GitHub work becomes a DAG with dependencies, roles, proof requirements, and human gates.
2. Run Fleet. The control plane schedules workers, validates mutation boundaries, tracks handoffs, and records durable proof.
3. Operate Cockpit. The GUI shows DAG state, worker lanes, graph context, preview-first actions, review packets, and audit history.
4. Improve the next run. Ledger events become standards, fixtures, gates, and review habits instead of disappearing into logs.

What You Get

Surface	What it shows
Fleet control plane	Go CLI, daemon, policy gates, schedulers, runners, evals, and SQLite-backed proof ledger.
Operator Cockpit	Electron Demo Lab surface for DAG attention, worker state, graph context, review packets, and preview-first actions.
Public demo media	GIFs and screenshots generated from fictional fixtures for README and release review.
Unified docs	Architecture, privacy boundary, limitations, migration manifest, release proof, and component entrypoints.
Proof lane	Root make proof, faster make release-scan, component proof, and public-boundary scans.

The Demo Lab screenshots are generated from the same fictional story pack as the tour GIF:

• Still hero frame
• Workers
• Atlas
• Preview-first action
• Ledger

Run Locally

No environment variables are required for the public demos.

make fleet-demo
make cockpit-demo

For full local proof:

make proof

make proof runs Fleet proof, installs Cockpit dependencies with npm ci, runs Cockpit proof, captures temporary Demo Lab media for readback, cleans local artifacts, and reruns the root privacy and whitespace gates.

For a faster publication-boundary scan:

make release-scan

Architecture

Harmony ships as one repo because the parts only make sense together:

• fleet/ is Harmony Fleet: the Go control plane and symphony CLI. It owns durable state, scheduling, policy, evals, worker runs, and side effects.
• cockpit/ is Harmony Operator Cockpit: the Electron GUI. It consumes Fleet-shaped snapshots and demonstrates the operator workflow through fictional Demo Lab replay data.
• docs/ is the launch and review spine: architecture, privacy, limitations, migration manifest, release proof, and reviewer routes.

See docs/architecture.md and fleet/docs/harmony-cockpit-contract.md for the component contract.

Public-Safe Guarantees

Real:

• the Go orchestration/control-plane code;
• the Electron cockpit and its four-page operator surface;
• the preview/apply boundary design;
• the standards, lessons, release proof, and privacy scans;
• the import manifest tying this unified repo back to the source components.

Fictional:

• Demo Lab issues, repos, comments, workers, review packets, and audit events;
• screenshots generated from the Demo Lab fixture;
• fake provider applies in the public cockpit demo.

Excluded from this repo:

• private Linear/GitHub state, local SQLite databases, worker logs, raw run history, credentials, provider payloads, personal workflow state, and client or hiring-sensitive material.

See docs/privacy.md for the full public boundary.

Review Path

1. Start with the docs index for the two-hop review map.
2. Read docs/architecture.md for component boundaries.
3. Read the migration manifest for source commits, import method, exclusions, and proof plan.
4. Read docs/release-proof.md before any visibility, tag, release, metadata, or launch-copy change.
5. Review docs/limitations.md for claims Harmony does not make.

Status And Limits

Harmony is a reference-quality open-source extraction of a private single-operator agent workflow. It is not a hosted SaaS, a multi-tenant control plane, or a live provider client.

Public release actions such as visibility changes, tags, releases, GitHub metadata, source-repo archiving, or launch copy remain operator-gated. Local proof can prepare those decisions, but does not perform them.

Contributing

Harmony is intentionally conservative:

• public artifacts must stay fixture-safe and credential-free;
• Fleet owns durable state and mutation authority;
• Cockpit must not write directly to Fleet databases, logs, worker workspaces, or provider APIs;
• future HTTP/RPC contract changes need focused contract tests;
• user-visible UI changes should include screenshot or media proof.

Start with CONTRIBUTING.md, SECURITY.md, and the nearest component docs before changing code.

License

Apache-2.0. See LICENSE and NOTICE.