Close the window. Come back to the work.
Quit the UI and local agent sessions keep running in the background. If the laptop sleeps, they pause with the machine; on wake, Harmony rechecks them and reattaches the same tabs and terminal history.
Harmony opens the coding agents you already use in one window, keeps them running when you close it, and lets them pass work to each other through one shared task list. Every item below says how finished it is, taken from our own capability inventory, so you can tell what works today from what we are still building.
Inventory v3.24.33-preview.2 · re-audited 2026-09-20 at v3.25.2-preview.1 · not re-checked against v3.25.8 · 22 capabilities · generated 2026-08-19
Running five coding agents is not five times one agent. They edit the same files at once, redo work another one already finished, and report success when all they did was write a plan. That is a coordination problem, and Harmony is the layer that solves it: one shared task list instead of five chat windows, agent-to-agent handoff that works across providers, and tabs and terminal history that survive a restart.
Most of this is not finished. Planning, spawning and the launch handshake appear below with the maturity our own capability inventory records for them, and none of the three is shipping yet. Neither is a delivery status that keeps sent, delivered and accepted apart: it is designed, not built. We would rather you read that here than find out after installing.
Everything below ships in the current build. All of it is labelled Preview: it works, and it may still change or differ by platform before we call it Stable.
Quit the UI and local agent sessions keep running in the background. If the laptop sleeps, they pause with the machine; on wake, Harmony rechecks them and reattaches the same tabs and terminal history.
Open coding CLIs in side-by-side tabs on one task list. You keep the providers you already pay for; Harmony does not resell tokens.
Send, ask, reply, and read an inbox between tabs. Handoffs survive a restart instead of living only in a chat paste.
Harmony finds the coding CLIs installed on your machine and starts any of them in a new tab: Claude Code, Codex, Cursor, Grok, Kimi, Gemini, Devin, OpenCode, and your own CLI. The model is always your own provider's; Harmony hosts none.
Speak into any agent tab. Speech is turned into text by a model running on your own computer.
The command-line client talks to the same workspace as the desktop app, so a script can list tabs, read a screen or send a prompt the way you would by hand, under the same permission checks.
Harmony's own coding agent, opened from the top bar and run with your own model key. It ships in preview and will not be called Stable until it has been checked on an installed package.
A separate host process owns long-running agent sessions, so reopening Harmony rejoins the session you left instead of starting a new one.
A Windows x64 installer with a published SHA-256 for every file. The download page says whether a build is code-signed; a checksum proves the file arrived intact, not who built it.
Apple silicon and Intel builds. Each one appears on the download page only once it is published, so there is never a link that goes nowhere.
The download page lists a Linux package only when it is published and the download can complete.
Every package records its version, release channel and source commit, so a bug report can name the exact build.
If the Pi coding agent is installed, one click opens it in a new tab.
When Harmony starts an agent session or hands it a prompt, it uses a structured call rather than pasting keystrokes into a terminal and hoping they land.
Work in design or active development stays here until it is ready to move into the shipping catalog.
Queued, delivered and accepted are shown as three different states, so a message that was only written is never presented as work another agent took on.
Describe an outcome and the agent answers with a plan: which agent takes which task, in what order, and which files it expects to touch. Nothing starts until you accept it. Design only in the inventory today.
One instruction becomes several working agents, each in its own tab with its own task. The spawner is a stub in the inventory: the surface exists, the automatic path does not. It is listed separately so the entry above does not imply it.
A launch hands the runtime an intent and waits for a handshake receipt, so a tab that exists is not mistaken for a process that started. Without it, the word running covers thinking, idle, out of quota and unreachable alike. Designed, not yet certified.
Shared, hosted sessions are a design today, not a feature. They are not offered locally or in Harmony Pro.
Download the free preview and try Harmony on your machine. Signing status and per-platform availability stay on the download page.
What's next
Download the free local preview for durable sessions, multi-tab workspaces, shared tasks, and agent messaging.
Free · Runs locally · No account needed