NanoClaw
NanoClaw version: latest (assessed March 2026)
CKP version: 0.3.0
Harness: @clawkernel/ckp-test v0.3.0
Live conformance (NanoClaw Bridge)
Section titled “Live conformance (NanoClaw Bridge)”The CKP bridge exposes stdio JSON-RPC handlers over NanoClaw runtime capabilities.
Core CKP vectors (31)
Section titled “Core CKP vectors (31)”Result:
- L1: 13/13 — CONFORMANT
- L2: 10/10 — CONFORMANT
- L3: 8/8 — CONFORMANT
- Overall: L3 CONFORMANT
Evidence:
CKP-A2A compatibility vectors (8)
Section titled “CKP-A2A compatibility vectors (8)”Current result:
- PASS: 0
- FAIL: 8
- SKIP: 0
- ERROR: 0
- Overall: A2A-NON-COMPATIBLE
Current scope:
reference/nanoclaw-bridgeimplements the CKP core wire surface- it does not currently implement the optional
claw.task.*A2A bridge methods - the A2A compatibility profile remains available as an additive target for future work
Native NanoClaw baseline (without bridge)
Section titled “Native NanoClaw baseline (without bridge)”NanoClaw natively exposes WhatsApp + internal container orchestration, not CKP stdio JSON-RPC. The table below is conceptual mapping, not wire-level conformance.
| CKP Primitive | NanoClaw Equivalent | Status |
|---|---|---|
| Identity | CLAUDE.md per group + assistant config | Implemented |
| Provider | Claude Agent SDK | Implemented |
| Channel | WhatsApp via baileys | Implemented |
| Tool | SDK tools + browser automation | Implemented |
| Skill | Skills engine with YAML manifests | Implemented |
| Memory | SQLite + filesystem + CLAUDE.md | Implemented |
| Sandbox | Docker / Apple Container isolation | Implemented |
| Policy | Implicit role/group-based restrictions | Partial |
| Swarm | Agent Teams (limited topology scope) | Partial |
Native core coverage: 7/9 implemented, 2/9 partial (Telemetry is optional and not part of core-level gating).
Native manifest-only harness baseline
Section titled “Native manifest-only harness baseline”Without a CKP bridge, NanoClaw cannot execute stdio JSON-RPC vectors. Manifest vectors still validate.
- L1 baseline: 4 pass, 9 skip, 0 fail — PARTIAL
This baseline is retained to show the gap between conceptual compatibility and protocol interoperability.
Why the bridge matters
Section titled “Why the bridge matters”The bridge converts native capabilities into CKP wire semantics (claw.initialize, claw.status, claw.tool.*, claw.memory.*, claw.swarm.*) so third-party tooling can test and integrate NanoClaw as a conformant CKP runtime.
See Compatibility overview for side-by-side results.