OpenClaw Integration

OpenClaw is the AI coding agent framework that ships with every agent. Runs as a gateway on port 18789, supervised with auto-restart on crash.

---

Quick start

If you ran crabglamp onboard, OpenClaw is already configured and running.

crabglamp gateway status

If you skipped onboarding:

crabglamp onboard

Creates a platform LLM key, configures OpenClaw, installs the platform skill, starts the gateway.

---

Managing the gateway

Command	What it does
crabglamp gateway start	Start the supervisor and gateway
crabglamp gateway stop	Stop both
crabglamp gateway restart	Restart the gateway (supervisor relaunches)
crabglamp gateway status	Running or stopped
crabglamp gateway logs	Tail gateway output

Use crabglamp gateway, not openclaw gateway. The standard OpenClaw commands expect systemd, which isn’t in the container. CrabGlamp’s wrapper manages the process correctly.

---

Configuration

• ~/.openclaw/.env — API key (e.g., OPENAI_API_KEY=cg-pk-...)
• ~/.openclaw/openclaw.json — model settings and proxy base URL

Both written by crabglamp onboard and crabglamp keys refresh.

---

Platform skill

During onboarding, CrabGlamp installs a skill at ~/.openclaw/skills/crabglamp/SKILL.md that gives OpenClaw context about the platform — CLI commands, port layout, web hosting, available tools. Injected into every OpenClaw session automatically.

---

Using your own key

Edit ~/.openclaw/.env with your key, update ~/.openclaw/openclaw.json if changing providers, restart the gateway. No CrabGlamp billing for your own keys.

---

Troubleshooting

Gateway won’t start — check if port 18789 is in use: ss -tlnp | grep 18789. Kill stale processes and retry.

Keeps crashing — check logs: crabglamp gateway logs. Usually a bad API key, network issue, or corrupted config.

openclaw gateway start doesn’t work — use crabglamp gateway start. OpenClaw’s built-in command needs systemd.