Current
HearthNet: Edge Multi-Agent Orchestration for Smart Homes
HearthNet deploys independent edge-resident agent runtimes across smart home devices, using OpenClaw as the execution platform and a dedicated librarian process to mirror coordination traffic for audit and recovery.
Signal
HearthNet: Edge Multi-Agent Orchestration for Smart Homes · local-edge-inference-trends · 2026-04-28 The project implements a smart home orchestration architecture where each functional role operates as an independent runtime on its respective edge device. Built on the OpenClaw framework, the system delegates coordination traffic to a dedicated librarian process that records external events into a shared repository, enabling audit trails and state recovery for the distributed agent network.
Context
Smart home IoT environments traditionally rely on centralized cloud orchestration, introducing latency, privacy friction, and single points of failure. HearthNet shifts this paradigm by distributing agent execution across local hardware, aligning with the broader infrastructure pattern of edge-resident runtimes and local-first orchestration. The explicit use of OpenClaw situates the system within the existing open-source agent runtime ecosystem, while the librarian pattern addresses a known gap in distributed system observability and recovery.
Relevance
The architecture operationalizes edge-native multi-agent coordination without cloud dependency. It demonstrates a concrete application of specification-driven orchestration and local-first state management. The librarian component introduces a lightweight, replay-capable audit mechanism that bridges runtime execution with post-hoc inspection, supporting the circuit for agent observability and state inspection.
Current State
The project is published as an academic/engineering signal with publicly available code, configuration templates, and replay scripts on GitHub. It functions as a reference implementation for edge-distributed smart home agents rather than a production deployment. The architecture remains framework-specific to OpenClaw but is structured to allow role isolation and traffic mirroring.
Open Questions
Interoperability with non-OpenClaw runtimes across heterogeneous edge devices. The actual latency and bandwidth overhead of the librarian traffic mirroring under concurrent role execution. How the shared repository handles conflict resolution and versioning when edge devices experience intermittent connectivity. Security boundaries for the replay scripts and audit logs in a residential network environment.
Connections
openclaw: runtime platform for edge-resident agent rolesagent-observability-state-inspection: librarian traffic mirroring and replay-based audit pattern