Harmonia Agent

The distributed evolutionary homoiconic self-improving agent.

Install from the Harmonia CLI product

Choose whether you want the full CLI Agent or the lightweight CLI App.

curl --proto '=https' --tlsv1.2 -sSf https://harmoniis.com/harmonia/install | sh

Installs the full CLI Agent runtime on your own machine.

Harmonia vs OpenClaw

Two agent frameworks. Different depth.

Self-improvement

Harmonia

Rewrites own source at runtime, hot-swaps compiled binaries, redistributes evolution across the organisation

OpenClaw

Writes new skills, edits prompts

Self-recovery

Harmonia

Crash history analysis, automatic patch generation, PID 1 supervision with restart and rollback

OpenClaw

Process restart only

Security

Harmonia

Encrypted vault, typed signal channels, taint propagation, policy gates, granular authorisation, invariant guards

OpenClaw

Opt-in Docker sandboxing. Phase 1 of 4

Secure browsing

Harmonia

3-layer sandbox with structured extraction. Agent never sees raw source code — only clean data

OpenClaw

Playwright. Not sandboxed by default

Memory

Harmonia

S-expression store with concept graphs, information-theoretic compression, and crystallization

OpenClaw

Markdown files + SQLite vector search

A2UI

Harmonia

21 rich components rendered natively on iOS, Android, Web. Text fallback everywhere else

OpenClaw

Text-only responses

Edge & industrial

Harmonia

x86 and ARM via OS⁴ — robotics, automotive, avionics, agriculture, logistics

OpenClaw

Node.js platforms only

Marketplace

Harmonia

Native: identity, wallet, contracts, bearer-cash payments

OpenClaw

Skill registry only

Remote control

Harmonia

Capability-scoped RPC over Tailscale: fs, shell, tmux, wallet. Wallet-derived Noise identity per node

OpenClaw

Not built-in

Multi-node

Harmonia

3 typed nodes (agent, TUI client, MQTT device). Noise protocol pairing. Bidirectional control

OpenClaw

Single-instance

Chat platforms

Harmonia

13 hot-pluggable channels

OpenClaw

28+ platforms via bridges

License

Harmonia

HCL-1.0 (Harmonia Community License)

OpenClaw

Open source

Full comparison with architecture details

What makes it different

Hot-swaps its own code at runtime

Ouroboros patches Lisp source and hot-swaps it into the running agent — no restart. Phoenix rolls out compiled Rust binaries under PID 1 supervision. Both validated by 6 safety gates. Failed changes automatically roll back.

Distributes evolution across the organisation

Genomic layer (source + policy) pushes to Git. Epigenetic layer (runtime state + patches) snapshots to persistent storage. Other agents in the fleet pull, replay, and recompile — even across different CPU architectures. Your entire fleet improves together.

Self-recovery and self-repair

Crash history analysis feeds automatic patch generation. Phoenix (PID 1 supervisor) restarts failed agents from the last known good state. Ouroboros reflects on crash patterns and writes targeted fixes. Recovery logs track every event for audit.

Security at every layer

AES-256-GCM encrypted vault with component-scoped access. Typed signal channels (no raw strings). Taint propagation across reasoning chains. Binary policy gates for 14 privileged operations. Granular authorisation with Ed25519 signature verification. Invariant guards the agent cannot disable.

Secure browsing and secure channels

3-layer browser sandbox: timeouts, domain allowlists, SSRF prevention. 11 extraction macros — the agent receives clean structured data, never raw source code. 18+ injection patterns scanned at signal entry. Dissonance scoring attenuates untrusted messages through harmonic routing.

Runs on edge and industrial devices

Via OS⁴, Harmonia runs natively on x86 and ARM hardware. Deploy on industrial robotics, IoT gateways, humanoid robots, automotive ECUs, avionics systems, agricultural equipment, and logistics fleets.

A2UI — Agent-Adaptive UI

21 rich components (forms, charts, cards, galleries, progress bars) rendered natively on iOS, Android, and Web. The agent decides what to show. The device decides how to render it. Every other channel gets automatic text fallback.

Memory with information-theoretic compression

S-expression encoded, not Markdown files. Nightly crystallisation scores entries by harmony, fact density, decision keywords, and access frequency. High-signal memories preserved. Low-signal compressed via pattern generalisation (Kolmogorov/Solomonoff). Concept graph tracks semantic relationships with domain classification.

TUI remote client with Tailscale pairing

Install just the TUI on any machine with --tui-only. It pairs with a remote Harmonia agent over Tailscale using the Noise protocol. The wallet derives per-node identity keys — no separate key management. Pairing sessions persist under ~/.harmoniis/harmonia/pairings/ for instant reconnection. The TUI always shows node context: harmonia@laptop → atlas@server [tailscale-client].

Capability-scoped remote control

Remote operations are typed RPC, not raw shell access. Client nodes expose adapters for filesystem, shell, tmux, wallet, and UI. Agent-to-agent links expose broader capabilities like gateway and baseband. Each adapter is independently permissioned. Every signal carries origin node, role, and channel class — baseband always knows what produced it.

Wallet as identity root

Each node derives its Tailscale identity from the HD wallet. Slot family tailscale-node/<label> provides the Noise key. Pairing keys derive under tailscale-link/<peer-id>. The /wallet command is a first-class TUI surface for managing keys, balances, and identity from any node.

3 node types. Secure pairing.

Every Harmonia node has a role. Pairing is cryptographic — no passwords, no accounts.

Agent

Full orchestrator. Runs Lisp + Rust. Controls LLM routing, evolution, memory, all frontends. This is the brain.

TUI Client

Lightweight remote terminal. Connects to an agent over Tailscale. Controls and is controlled by the agent. Includes wallet for identity.

MQTT Device

IoT, mobile, or XR device. Connects via MQTT. Agent can manipulate A2UI, push notifications, and device-specific resources remotely.

Pairing workflow

1. Install with --tui-only on the client machine. This sets up the TUI, Tailscale frontend, and derives a Noise keypair from your wallet.

2. The agent generates a one-time pairing code. Paste it into the TUI client.

3. Noise handshake completes. Session saved under ~/.harmoniis/harmonia/pairings/. Reconnection is automatic.

Every node derives its identity from the HD wallet — slot family tailscale-node/<label> for the local key, tailscale-link/<peer-id> for pair state. No separate key management.

Bidirectional remote control

Pairing is not one-way. The agent can control the TUI client's filesystem, shell, and tmux — and the TUI client can control the agent. Every operation is capability-scoped RPC, not raw shell access.

The TUI always shows the active context: harmonia@laptop → atlas@server [tailscale-client]. Agent-to-agent links expose broader capabilities like gateway and baseband access. Three channel classes keep signals distinct: tailscale-client, tailscale-agent, and mqtt-device.

13 frontends. Hot-pluggable.

Each frontend is a Rust .so that can be loaded at runtime. Add or remove channels without restart.

TUI
Telegram
Slack
Discord
Signal
WhatsApp
iMessage
Mattermost
Nostr
Email
MQTT
HTTP/2
Tailscale

A2UI — Agent-Adaptive UI

21 rich components rendered natively on iOS, Android, and Web: forms, charts, image galleries, progress bars, cards, tabs. The agent decides what to show — the device decides how to render it. Every other channel gets automatic text fallback.

Architecture

Lisp orchestrates. Rust executes. 9 explicit ports. 39 native crates.

vault

Encrypted secrets

store

Runtime config

router

LLM completion

lineage

Git versioning

matrix

Route constraints

tool-runtime

Browser, search, voice

baseband

13 frontend channels

swarm

Parallel agents + CLIs

evolution

Self-rewrite

Runs natively on macOS, Linux, Windows, FreeBSD. Via OS4, deploy on x86 and ARM industrial and edge hardware. Full architecture docs

Plans

Community

Free

  • + Full agent capabilities
  • + All 13 frontends
  • + Self-improvement
  • + Bring your own OpenRouter key
  • + Organisations allowed (HCL-1.0 — no revenue threshold)
  • + Community support

Individual

$20/mo

  • + Managed instance
  • + LLM budget included (limited)
  • + Harmonia App on all platforms
  • + Automatic updates
  • + Email support
  • + 1 user

Basic

$100/mo

  • + Everything in Individual
  • + 7x LLM budget
  • + Organization management
  • + Up to 5 users
  • + Priority support

Pro

$200/mo

  • + Everything in Basic
  • + 20x LLM budget
  • + Up to 10 users
  • + Custom model routing
  • + Advanced analytics

Enterprise

Custom

  • + Unlimited users
  • + Dedicated infrastructure
  • + Custom LLM budget
  • + 24/7 premium support
  • + SLA guarantees

Full pricing details

FAQ

What does "self-improvement" actually mean?

Harmonia rewrites its own Lisp source code at runtime (Ouroboros) and hot-swaps compiled Rust binaries (Phoenix). Every change goes through 6 safety gates. Failed changes automatically roll back. Improvements redistribute across agent fleets via Git and persistent storage.

What is the difference between Community and paid plans?

Community is free and self-hosted — you bring your own OpenRouter key and pay LLM providers directly. Paid plans include a managed Harmonia instance with LLM budget included: Individual (limited), Basic (7x), Pro (20x). Paid plans also include the Harmonia App with A2UI, automatic updates, and priority support.

Can organisations use the Community plan?

Yes. The Harmonia Community License (HCL-1.0) permits organisations of any size to use, modify, and deploy Harmonia freely. The only restriction is offering Harmonia as a hosted service for third parties — that requires a separate commercial license. For managed infrastructure and higher LLM budgets, see paid plans.

What makes the memory system different?

S-expression encoding with information-theoretic compression. Nightly crystallisation scores memories by harmony, fact density, decision keywords, and access frequency. High-value entries are preserved; low-signal entries compress via pattern generalisation. A concept graph with domain classification tracks semantic relationships across all memories.

What is A2UI?

Agent-Adaptive UI. 21 rich components (forms, charts, cards, galleries, progress bars) rendered natively on iOS, Android, and Web. All other channels get automatic plain-text fallback. Available through the Harmonia App on paid plans.

What is OS⁴?

A FreeBSD-based operating system with Harmonia integrated as a native runtime. Supports x86 and ARM. Used in industrial robotics, automotive, agriculture, avionics, and logistics.

What is the CLI App?

A lightweight install (--tui-only) that gives you a terminal interface to a remote Harmonia agent over Tailscale. It includes the TUI frontend, the Tailscale frontend, and a local wallet for identity — but not the full orchestrator or LLM routing. Pair with your agent using a one-time code and you're connected.

How does Tailscale pairing work?

Both nodes derive Noise protocol keys from their HD wallet. The agent generates a one-time pairing code. Paste it into the CLI App. The Noise handshake establishes a secure session, persisted under ~/.harmoniis/harmonia/pairings/. Subsequent connections are automatic.

Can the agent control my remote machine?

Yes — pairing is bidirectional. The agent can access the CLI App's filesystem, shell, and tmux via capability-scoped RPC. The CLI App can equally control the agent. Every operation is permissioned and the TUI always shows node context. You can also manage your wallet from any node via /wallet.