Local by default. Cloud by choice.
Harmony runs on your machine, free, and that does not change. When a job is bigger than your laptop or longer than your evening, send one agent or several to a hosted machine. They keep working after you close the lid, signed in with your own Claude Code or Codex subscription, and you pick up where they left off. Harmony Pro is hosted compute, not model tokens: model usage is billed by your provider, not by us, so you never pay twice for it.
Harmony Pro is in early access. You can subscribe or start the free trial today, and we are still proving it with our first customers.
Harmony Pro
$29/month
Your agents keep working in the cloud after you close the lid.
Try it with 5 Agent Hours, free.
No card. When the hours run out, nothing is charged and Harmony keeps working locally.
01 / SEND
One agent, or several at once
Pick what leaves your machine: one agent's tab, or several. Each sends that repository's uncommitted work, meaning staged and unstaged changes plus the untracked files you choose, and which agent it was running, so the hosted machine starts the same one. Your tab layout, task board and terminal history stay on your machine. You see the file list before anything goes.
02 / STACK
Queue the next prompts and close the lid
Stack prompts and your agent works them in order while the laptop is shut. The queue lives on the server, so sleeping, disconnecting or rebooting changes nothing about the work.
03 / RESTORE
Pick the session back up anywhere
Run harmony -r to list restorable sessions, local and cloud, and reattach to one. The same terminal, the same history, from the desktop app or any terminal you have.
04 / BRING HOME
Results land in your checkout, not a download
Bring Home applies the work back to your local repository and tells you if anything diverged while the workspace ran. Export is never metered.
Step 1
Install Harmony
curl -fsSL https://ideharmony.com/install.sh | shRuns entirely on your machine. No account, no signup.
Step 2
Run something locally
harmonyThis is the whole product, free forever. The cloud is optional.
Step 3
Sign in when you want hosted compute
harmony loginOpens a browser to approve this device. The 5 Agent Hours trial is started separately from your account, with no card.
Step 4
Send your work to a cloud workspace
harmony cloud newYour uncommitted changes go with it. Known sensitive paths (.env, SSH keys, cloud config) are refused when the manifest is built. You review the selected file list before you send.
Step 5
Bring the results home
harmony cloud bring-homeApplies the work back to your local checkout, and tells you if anything diverged.
Cloud adds. It never takes away.
| Harmony Core | Harmony Pro | |
|---|---|---|
| Runs on your machine | Yes | Yes. Harmony Pro adds hosted workspaces; it does not replace local |
| Account required | No | Yes |
| Price | Free forever | $29/month |
| Model access | Your own provider keys, on your machine | Your own subscription, signed in inside the workspace |
| Hosted compute | None | 60 Agent Hours each month, on the monthly and annual plan alike |
| Parallel work | Limited by your machine | 3 workspaces at once |
| Your code leaves your machine | Core does not upload the workspace. Chosen agents may transmit. | Only what you send, and only when you send it |
| Works offline | Local UI, yes. Remote providers need a network. | Local work continues; hosted workspaces need a connection |
One Agent Hour is one hour on a Standard machine. Larger machines use hours faster. Agent Hours are cloud machine time, not model tokens.
Stored, and why
Account email
Sign-in and billing correspondence. Kept: Until account deletion.
Workspace filesystem contents
It is the workspace. Kept: While the workspace exists, plus 30 days after cancellation.
Usage records (seconds per workspace)
Billing, and answering 'where did my hours go'. Kept: Kept after workspace deletion, so an invoice stays explainable.
Device sessions
Keeping you signed in on machines you approved. Kept: Until revoked or expired.
Repository tokens you choose to save
So a cloud workspace can reach a private repository. Optional, saved under Account → Secrets; provider and model API keys are refused. Kept: Encrypted at rest with the server's master key, until you remove them or delete the account.
Credential handling and payment details
Model provider API keys
Harmony does not harvest provider API keys into a Harmony vault, and it does not put secrets in metadata. Auth stays with the CLI you chose: that CLI's own login or a local environment variable on the machine where the CLI runs. Local Core is not a Harmony gateway. On Cloud, sign the agent in inside the workspace the same way. The optional secret store under Account → Secrets holds repository tokens only and refuses provider and model API keys. Handoff still refuses known sensitive paths (.env, SSH keys, cloud config) when the manifest is built. Review the selected file list before you send. That is a path check, not a promise that every secret is excluded.
SSH keys, cloud credentials, .env files
Refused when the handoff manifest is built. They are never added and filtered out later.
Secrets in logs
Log lines pass through a redactor that matches by name and by shape.
Card numbers
Payment details go to Stripe directly and never touch our servers.
Reliability, stated plainly
We don't offer a uptime SLA yet. We'd rather say that than publish a number we have no track record behind.
- Usage is confirmed against a running lease. A failed start is investigated; unknown or unreconciled time is not automatically free.
- If we're down, Harmony keeps working on your machine. The local product doesn't depend on us.
- A pause persists normal storage. That is not a guarantee that every file can be recovered.
If hosted compute fails on our side, write support with the workspace id so we can investigate. Credit rights follow the Cloud Terms.
Before you send anything
Try it with 5 Agent Hours, free
No card. When the hours run out, nothing is charged and Harmony keeps working locally.
Already subscribed? Open your Cloud account.