ZeroClaw Guide

Deploy the ultra-lightweight Rust agent on Maritime.

Overview

ZeroClaw is a single Rust binary that exposes a gateway plus an OpenAI-compatible chat API. It uses a fraction of the memory of Node.js-based agents (typically <5 MB resident) and starts in under a second, which makes it a good pick for high-density fleets.

Docker Image

Image: ghcr.io/zeroclaw-labs/zeroclaw:debian

Debian-based runtime, gateway on port 42617, HOME is /zeroclaw-data.

How It Works

Maritime wraps the entrypoint so the daemon (a) runs zeroclaw config migrate first, (b) is patched to bind 0.0.0.0 with allow_public_bind = true, and (c) has device pairing disabled so the Maritime proxy can connect directly. The WebSocket sub-protocol is zeroclaw.v1.

# The container runs with:
ZEROCLAW_HEADLESS=true
ZEROCLAW_ALLOW_PUBLIC_BIND=true
ZEROCLAW_GATEWAY_PORT=42617
ZEROCLAW_GATEWAY_PASSWORD=<auto-generated>
ZEROCLAW_WORKSPACE=/zeroclaw-data/workspace

Environment Variables

ZeroClaw uses an OpenAI-compatible provider. If you don't supply OPENAI_API_KEY /ANTHROPIC_API_KEY, Maritime injects a per-agent proxy token pointed at https://api.maritime.sh/api/llm/v1.

Deploy

Select Template → ZeroClaw Agent in the Create Agent modal, or:

maritime create -n my-agent -t zeroclaw --tier smart && maritime deploy my-agent