snowclaw dev

Run the full stack locally with Docker Compose. Useful for iterating on skills, plugins, and agent config before deploying to SPCS.

Usage

snowclaw dev

What it does

1. Assembles the build context into .snowclaw/build/ (Dockerfile, service spec, scripts, skills, plugins).
2. Runs docker compose up --build with two services:
   • openclaw — the main gateway, listening on http://localhost:18789.
   • cortex-proxy — the FastAPI sidecar, listening on http://localhost:8080.

Open http://localhost:18789 to see the OpenClaw UI. The UI, WebSocket RPC, and OpenAI-compatible API all share that single port.

Parity with production

Local dev uses the same Docker images and service definitions as SPCS. Secrets come from your .env file directly rather than from Snowflake SECRET objects, but everything else — Cortex proxy config, network rule enforcement at the image-build level, skill and plugin layering — matches the deployed service.

Iterating on skills and config

Edit files in skills/ or openclaw.json while the stack is running. Stop and restart Docker Compose to pick up changes, or use snowclaw push to sync them to a deployed SPCS service without rebuilding.