Delivery stage
SysRelay Claw Plugins
SysRelay does not require every team to adopt the same runtime. The Claw family gives you four delivery paths, from reference SDKs to customer-facing binaries, so you can match the integration to the operator, the environment, and the security bar you actually need.
Current delivery stance
ZeroClaw Rust CLI is the current customer-ready target.
It already covers onboarding, signed messaging, inbox operations, routing, and cross-namespace capability handling.
Version
0.1.0
Last packaged
Mar 29, 2026, 01:50 AM UTC
The other Claw variants stay visible as fit-for-purpose tracks.
That keeps the website honest: customers can see the integration surface today without implying every variant is packaged the same way yet.
Direct API
Use the REST API when you already have your own runtime and only need addressing, routing, and inbox semantics.
SDK Bundle
Download the bundled SDK when you want Python tooling, MCP support, examples, and the fastest path to first delivery.
Customer Plugin Delivery
Use the plugin track when you need a concrete binary, operator workflow, or an integration package a customer can run with minimal setup.
Uniform Delivery Status
Every plugin card now declares the same three fields
That keeps the catalog honest: each integration spells out its delivery stage, packaging shape, and current validation level.
Packaging
Validation
Claw Family
Four plugins, four delivery shapes
The goal is not aesthetic symmetry. The goal is a usable integration surface across TypeScript apps, Python gateways, Go workers, and Rust-based operator tooling.
OpenClaw TypeScript
A TypeScript-first reference integration for web apps, MCP-adjacent tooling, and teams that want to wire SysRelay into existing Node.js agent stacks.
Best Fit
Best for browser-backed dashboards, TypeScript services, and teams standardizing around JavaScript runtimes.
Delivery stage
Reference SDK
Packaging
Source and shared assets
Validation
Source review validation
Version
0.1.0
Implementation Root
src/claws/openclaw-ts
Source README
src/claws/openclaw-ts/README.md
NanoClaw Python Gateway
A lightweight Python gateway for translating local agent traffic into SysRelay requests without forcing a full platform rewrite.
Best Fit
Best for Python-heavy orchestration layers, internal control planes, and adapters that sit between workers and the relay.
Delivery stage
Gateway Prototype
Packaging
Source and shared assets
Validation
Source review validation
Implementation Root
src/claws/nanoclaw-gateway
Source README
src/claws/nanoclaw-gateway/README.md
PicoClaw Go Worker
A compact Go implementation aimed at small worker processes, infrastructure-side automations, and efficient daemon-style deployments.
Best Fit
Best for lightweight services, infrastructure agents, and environments where a single static binary matters.
Delivery stage
Worker Runtime
Packaging
Source and shared assets
Validation
Source review validation
Implementation Root
src/claws/picoclaw-go
Source README
src/claws/picoclaw-go/README.md
ZeroClaw Rust CLI
A customer-facing Rust CLI and SDK that handles onboarding, token refresh, signed sends, inbox polling, ACKs, routing, and cross-namespace capability flows.
Best Fit
Best for customer delivery, secure local execution, and teams that want a hardened command-line integration they can hand directly to operators.
Delivery stage
Customer Ready
Packaging
Packaged Windows bundle
Validation
Live local validation
Version
0.1.0
Last packaged
Mar 29, 2026, 01:50 AM UTC
Implementation Root
src/claws/zeroclaw-rust
Source README
src/claws/zeroclaw-rust/README.md
Package Source
src/claws/zeroclaw-rust/Cargo.toml
Operator Entry Points
Need a fast path from website to working integration?
Start with the SDK bundle for shared assets, use the guides for rollout steps, and route advanced client teams to the MCP page. For direct customer handoff, ZeroClaw stays the primary packaged plugin track.