Documentation

Marketplace, Wallet, Harmonia, SDK, and OS4

View as Markdown

Harmonia vs OpenClaw

Two agent frameworks. Different product models.

OpenClaw is a personal AI assistant with broad chat coverage and a simpler operational model.

Harmonia is a distributed evolutionary agent family. It separates public products into Agents and Apps, with both CLI and GUI interface families, and routes them through a typed gateway with strong policy and transport boundaries.

Comparison

Capability Harmonia OpenClaw
Self-improvement Rewrites own Lisp source (Ouroboros), rolls out compiled binaries (Phoenix), and redistributes evolution across agent fleets Writes skills and edits prompts. No source-level self-modification of the core runtime
Security kernel Non-bypassable: typed signal dispatch, taint propagation, policy gates, invariant guards Opt-in Docker sandboxing
Browser 3-layer sandbox with structured extraction. Agent does not ingest raw HTML as normal operating input Playwright/CDP style browser automation
Adaptive interfaces GUI Apps render A2UI-rich surfaces on mobile, web, XR, and desktop GUI while CLI App remains terminal precise Text-based responses
Remote control CLI and GUI Apps pair with agents over Tailscale, MQTT mTLS, and HTTP/2 mTLS with typed remote capabilities Not built-in
Product topology CLI Agent, GUI Agent, CLI App, and GUI Apps around one runtime Single-instance assistant model
Gateway frontends 13 hot-pluggable frontends including TUI, MQTT, HTTP/2, chat, email, and device channels 28+ chat platforms via bridges
Marketplace Native wallet, identity, bearer-cash, contracts, and paid messaging Skill registry only
Architecture targets macOS, Linux, Windows, FreeBSD, OS⁴, mobile GUI, browser GUI, XR GUI Node.js platforms
Managed deployment Managed Agent plus self-managed agent forms Self-hosted only
License HCL-1.0 (Harmonia Community License) Open source

Product Model

The biggest difference is that Harmonia has a clean public product taxonomy:

Interface Agent App
CLI CLI Agent CLI App
GUI GUI Agent GUI Apps
  • Agents run Harmonia
  • Apps connect to agents

Managed cloud is a deployment mode of an agent, not a separate product class.

That structure makes it possible to explain how desktop GUI can be either a remote app or a local agent without inventing new public categories.

Remote Surfaces and Transport

OpenClaw does not define a first-class remote client topology.

Harmonia does:

  • CLI App is the TUI remote client from the same CLI product as the CLI Agent
  • GUI Apps cover iOS, watchOS, tvOS, Android, Web, OpenXR, and desktop GUI remote mode
  • CLI Agent / GUI Agent / Managed Agent are the runtimes those apps connect to

Transport depends on surface:

  • Tailscale for CLI App and desktop GUI remote mode
  • MQTT mTLS for iOS, watchOS, tvOS, Android, and OpenXR GUI Apps
  • HTTP/2 mTLS for the Web GUI App

Apps are not just chat shells. They can expose files, notifications, device context, and other policy-scoped resources to the agent.

Memory and Runtime Depth

OpenClaw stores memory in files and vectors. Harmonia uses a deeper runtime model:

  • S-expression memory
  • information-theoretic crystallisation and compression
  • concept graph with domain classification
  • typed signal routing through the gateway
  • policy-aware transport and payment/auth layers

This makes Harmonia structurally closer to a programmable operating environment than to a chat-first assistant framework.

When to Choose Harmonia

  • You want a clear agent/app topology instead of a single-instance assistant model
  • You need CLI and GUI remote surfaces around the same agent runtime
  • You need typed remote control over Tailscale, MQTT mTLS, and HTTP/2 mTLS
  • You want self-improvement, strong policy gates, and wallet-rooted identity
  • You want marketplace-native payments, contracts, and accounting

When to Choose OpenClaw

  • You want the broadest chat platform coverage
  • You prefer a simpler assistant model over a multi-surface agent runtime
  • You want fully open-source licensing on day one
  • You want to stay in the Node.js ecosystem

Next Steps