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.
Open the coding CLIs you already use in one window, keep their sessions running when you close it, and let them hand work to each other across providers through a shared task board and a durable inbox. 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 · 22 capabilities · generated 2026-08-19
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.
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 board instead of five chat windows, agent-to-agent handoff that works across providers, tabs and terminal history that survive a restart, and a status you can trust, because sent, delivered and accepted are not treated as the same thing.
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. We would rather you read that here than find out after installing.
Stable, Beta, and Preview capabilities ship in the current product. Preview availability can still vary by platform.
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 board. 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.
Launch routes and top-bar providers for the coding CLIs on your machine. Connect Claude Code, Codex, Cursor, Grok, Kimi, Gemini, Devin, OpenCode, and your own CLI without a Harmony-hosted model.
Dictate into the workspace with an on-device voice path. Core workspace features do not require a Harmony website account.
The nala CLI talks to the same local workspace process as the desktop app. Install commands and screen reads use the same identity path.
A published Windows x64 installer with per-artifact SHA-256. Signing status is shown on the download page; integrity checks are not code signing.
macOS arm64 and Intel installers when published on the channel. Unpublished targets stay off the download grid rather than offering a dead link.
Linux packages when published on the channel. The download page lists only artifacts that can complete.
Release metadata carries version, channel, and commit so you can tell which build you installed.
Launch a Pi TUI session from the desktop top bar when that provider is installed on the machine.
Session create and prompt flows go through typed RPCs rather than ad-hoc paste into a bare terminal.
A top-bar first-party agent with real model turns. Preview: it ships in the preview channel; not Stable until installed package proof is in the inventory.
A host process owns long-running agent sessions so reattach is a rejoin, not a restart from zero.
Work in design or active development stays here until it is ready to move into the shipping catalog.
Message and task delivery states stay distinct so a successful write is not presented as an accepted handoff.
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.
Hosted multiplayer is design-only in the inventory. Not offered on the free local preview.
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