I’d like to propose adding support for running OpenClaw on devices that do not require Linux or Node.js — such as embedded systems, microcontrollers, and ultra-low-resource hardware.
refer to: https://github.com/memovai/mimiclaw

Today, OpenClaw relies on the Node.js runtime and typical OS environments (Linux/macOS). This makes it hard to run OpenClaw on devices that cannot host an OS or a high-level runtime, such as IoT boards or single-chip microcontrollers.

Why this matters

There is a growing demand for ultra-light, private, always-on AI assistants that:

• run on devices with no OS (bare-metal or minimal firmware),
• do not depend on Node.js or heavyweight runtimes,
• operate under tight memory / power constraints,
• keep user memory local and privacy-first.

These use cases are increasingly relevant for edge AI, personal devices, and privacy-sensitive environments.

Reference implementation: MimiClaw

As a concrete reference, I built MimiClaw:

👉 https://github.com/memovai/mimiclaw

MimiClaw demonstrates that an OpenClaw-style agent loop can run on a $5 ESP32-S3 microcontroller, with:

• no Linux, no Node.js,
• a pure C runtime,
• Wi-Fi connectivity,
• Telegram as the interaction interface,
• local memory persisted across reboots,
• tool invocation in a constrained environment.

This shows that OpenClaw’s core agent concepts can be adapted to embedded platforms.

Proposal

To make OpenClaw more portable and future-proof, it would be great to consider:

• Decoupling core agent logic from the Node.js runtime,
  so alternative runtimes (C/C++, Rust, WASM) can implement the same agent loop.

• Defining a runtime-agnostic agent interface / protocol
  (e.g., JSON schema for tool calls, memory, loop state).

• Separating platform-specific adapters (filesystem, process, networking)
  from the agent core.

• Optionally providing documentation or reference implementations
  for lightweight or embedded runtimes.

Discussion

• Would the team be open to making OpenClaw’s core more runtime-agnostic?
• Are there any plans to support WASM or other lightweight execution environments?
• Would a minimal “agent core spec” be useful for third-party ports like embedded devices?

Thanks for building OpenClaw — this proposal is meant to expand its reach to edge and embedded scenarios while keeping the core design intact. Looking forward to your thoughts!