mlclaw

name

mlclaw

description

Use when setting up, operating, migrating, repairing, or explaining an OpenClaw deployment on Hugging Face with the ML Claw `mlclaw` CLI. Covers the browser Space gateway, Hugging Face OAuth, local gateway mode, private Storage Buckets, Telegram as an optional connector, Docker context pinning, model selection through the Hugging Face Router, OpenAI API key setup, costs, diagnostics, and state safety.

ML Claw

Core Rule

Use the mlclaw CLI as the source of truth. Do not hand-create Hugging Face Spaces, buckets, secrets, or Docker containers unless debugging a failed mlclaw operation. Keep bootstrap credentials local to the user's machine. Space OAuth credentials may be stored only through ML Claw's encrypted, process-isolated integration store.

Default to the browser Space gateway unless the user explicitly asks for local gateway mode.

What ML Claw Creates

An ML Claw deployment has:

• a private Hugging Face Storage Bucket for durable OpenClaw state snapshots;
• a private Hugging Face Docker Space for the default browser gateway;
• no explicit Space hardware request by default; Hugging Face assigns the default free CPU hardware unless --hardware or a feature requiring paid hardware is used;
• a prebuilt ghcr.io/huggingface/mlclaw runtime image by default;
• Hugging Face OAuth enabled on the Space;
• automatic Hugging Face MCP and Research Agent integrations authorized by an admin-only OAuth step after ordinary Hugging Face sign-in;
• a local deployment manifest under ~/.config/mlclaw/deployments/;
• local secrets under ~/.config/mlclaw/secrets/;
• app Spaces mount the private Storage Bucket read-write at /data/mlclaw-state for snapshot storage without storing the user's broad Hub token in the Space;
• preinstalled Hugging Face tooling in the OpenClaw workspace, including , , , HF Python libraries, and baseline Hugging Face Agent Skills mirrored into both and ;