hmharness logo

hmharness

Free

A self-evolving agent framework built for the full HarmonyOS/OpenHarmony development lifecycle—featuring a zero-dependency core, self-evolution as a first-class citizen, leverage of the MCP ecosystem, and headless ful...

Visit Website
Related by shared tags and keywordsberimorAn agent harness for local modelsopenamer
ai-agentagent-frameworkarktsarkuiautomationaiai assistant

Overview

hmharness is a self-evolving agent framework for HarmonyOS/OpenHarmony development, described as a cross-environment Cognitive Runtime. It provides a zero-dependency kernel, treats self-evolution as a first-class citizen, and leverages the MCP ecosystem. The framework can create a project, build it, install it on a device, and run it in an emulator from a single command. It is a monorepo of 13 packages with 0 runtime dependencies in the kernel, 809 unit tests, and 5 environment adapters. The project is a clean-room rewrite that does not inherit any upstream runtime capabilities. The self-evolution mechanism references public research ideas such as Darwin Gödel Machine, GDPevo, and Penguin Harness, with no code copying. hmharness is an independent community open-source project under the MIT license, not affiliated with Huawei or the OpenAtom Foundation.

Pricing

Free

Detailed plans have not been confirmed in our catalog. Check the official website for current limits and billing terms.

Visit Website

Prices and limits may change. Confirm the currency, billing period, seat minimum and usage caps on the official website.

Use Cases

  • Teams use hmharness to create a HarmonyOS project with multiple pages and modules in a single call.
  • Developers use hmharness to manage the full lifecycle of an emulator without opening DevEco Studio.
  • Teams use hmharness to build, install, launch, and uninstall HarmonyOS applications on devices.
  • Developers use hmharness to run continuous self-evolution with dual gates and automatic rollback on regression.
  • Users use hmharness to connect to MCP community servers and expose HarmonyOS toolchain to MCP hosts.
  • Operators use hmharness to monitor open-source HarmonyOS ecosystem changes via a daily radar.
  • Users use hmharness to interact via a full-screen TUI or web interface with session replay and workspace switching.
  • Teams use hmharness to route different tasks to different OpenAI-compatible providers.

Features

Support the HarmonyOS development lifecycle

Support OpenHarmony development workflows

Use a zero dependency core

Enable agent self evolution

Work with the MCP ecosystem

Control emulators and toolchains headlessly

Reviews

No reviews yet. Be the first to share your experience!

Rankings & collections