Research notes

Candidate decisions and relationship context from the 2026-06-11 verification pass.

The latest follow-up resolved source-backed candidate decisions: secure-openclaw and openclaw-composio are published as Composio OpenClaw variant/context entries, skillshare is published as ecosystem skills infrastructure, ESP-Claw remains OpenClaw-inspired adjacent IoT hardware-agent context, nanobot remains an OpenClaw-compatible adjacent agent, Qwen is provider/model infrastructure, and ChatGLM has no direct OpenClaw evidence and remains adjacent model infrastructure.

Read context Pulse archive

Published adjacent context

One more item can move from caveat to adjacent tooling.

Published items remain outside the primary variant count.

Published: claw-harbor

OpenClaw evaluation adapter with Apache-2.0 license, tests, docs, and release history.

Published: Agent Sessions

Mature adjacent session/history tooling with OpenClaw and Hermes support.

Published: nanobot

OpenClaw-compatible adjacent personal AI agent. It is not labeled a core OpenClaw variant because the relationship evidence is compatibility, skill metadata, ClawHub support, and ecosystem overlap.

GitHub source ↗

Published: ESP-Claw

OpenClaw-inspired IoT hardware-agent framework from Espressif. It is not labeled a core OpenClaw fork because the README says it is inspired by OpenClaw and reimplemented in C.

GitHub source ↗

Published: secure-openclaw

Composio OpenClaw-like assistant with messaging, memory, reminders, and 500+ integrations. Published as integration-focused variant/context, not as the upstream baseline.

GitHub source ↗

Published: openclaw-composio

Composio authentication integration fork for OpenClaw. Bundled with secure-openclaw to avoid double-counting closely related Composio work.

GitHub source ↗

Published: skillshare

Cross-tool OpenClaw skills infrastructure for syncing and sharing skills across AI CLI tools.

GitHub source ↗

2026-06-11 candidate decision

ESP-Claw relationship label.

ESP-Claw

Decision: publish as OpenClaw-inspired adjacent IoT hardware-agent context. Evidence includes Apache-2.0 license, active Espressif public source, README description as a Chat Coding AI agent framework for IoT devices, and explicit README wording that it is inspired by the OpenClaw concept and reimplemented in C. Avoid counting it as a core OpenClaw fork.

Source

High-attention cache re-check

nanobot, Qwen, and ChatGLM relationship labels.

nanobot

Decision: publish as an adjacent OpenClaw-compatible agent. Evidence includes MIT license, active public source, openclaw GitHub topic, ClawHub support, OpenClaw-style skill metadata, and OpenClaw-derived channel implementation references. Avoid calling it an OpenClaw fork or core variant.

Source

Qwen

Decision: keep as model/provider context, not a variant. QwenLM/Qwen is Alibaba Cloud model infrastructure; OpenClaw relevance comes from OpenClaw bundled Qwen/Qwen Cloud/DashScope provider documentation and plugin metadata.

Source

ChatGLM

Decision: keep as adjacent model infrastructure/watch context. ChatGLM3 documents tool invocation, code interpreter, and agent tasks, but no public README or repository evidence tied it directly to OpenClaw during this pass.

Source

2026-06-11 Composio candidate decisions

secure-openclaw and openclaw-composio move out of the queue.

secure-openclaw

Decision: publish as an integration-focused OpenClaw variant/adjacent distribution. Evidence includes MIT license, OpenClaw-specific topics, 1,204 stars, 165 forks, and README/description language about a personal 24x7 AI assistant like OpenClaw with messaging platforms, persistent memory, scheduled reminders, and 500+ app integrations. Caveat: do not treat it as the upstream baseline.

Source

openclaw-composio

Decision: publish as the companion Composio authentication integration fork, bundled with the Composio context rather than counted as a separate primary variant. Evidence includes MIT license and source description as an OpenClaw fork with integrated Composio plugin for easy tool authentication and credential handling.

Source

skillshare

Decision: publish as adjacent OpenClaw skills infrastructure, not a variant. Evidence includes MIT license, active source, OpenClaw topics, and explicit support for syncing skills across Codex, Claude Code, OpenClaw, and more.

Source

Watchlist

Still promising, not promoted.

iClaw / open-iClaw-app

Android alpha releases exist, but source code/license evidence remains insufficient for publication.

AIRIClaw

OpenClaw gateway/skill references exist, but license and release evidence remain missing.

S3pia

Active adjacent assistant, but evidence supports inspiration/adjacency rather than direct OpenClaw integration.

Orkas

Active multi-agent desktop client with OpenClaw/Hermes topics; watch as adjacent orchestration.

OpenBiliClaw

Active content discovery agent; watch because direct OpenClaw developer-tooling evidence is not established.

Proofrail for OpenClaw

Explicit OpenClaw guardrail tooling; watch until adoption/maturity improves.

Re-verification queue

PocoClaw still needs a current source URL. SwarmClaw, DashClaw, Clawrium, GitClaw, ClawHub, AlphaClaw, ClawTeam-OpenClaw, and OpenSquilla now have source URLs and are carried as watch/infrastructure context until deeper inspection supports publication without inflating variant counts.