Overview
Overview of the OpenClaw sandbox setup flow for Cue users
Use OpenClaw when you want a full agent runtime inside a Cue Computer, the agent's own Linux machine.
Cue CLI and OpenClaw are separate runtimes. Cue uses ~/.cue/.... OpenClaw uses ~/.openclaw/....
This section is for sandbox and code-server environments where you want a copyable setup path with minimal manual editing.
What You Will Do
- Install OpenClaw
- Run non-interactive onboarding
- Configure Discord
- Configure Telegram if needed
- Configure WhatsApp if needed
- Configure Feishu / Lark if needed
- Verify model auth
Setup
Install OpenClaw and initialize ~/.openclaw in the sandbox
Discord
Add the bot token, start the gateway, and approve pairing
Telegram
Add the bot token, run the gateway in the sandbox, and approve pairing
Link a WhatsApp Web session, enable self-chat mode, and test on your own number
Feishu / Lark
Add the app credentials, start the gateway, and approve pairing
Model Auth
Set the default model and verify the assistant can answer
Quick Start
Install OpenClaw in the sandbox terminal:
npm install -g openclaw@latest
openclaw --versionThen continue to Setup.
Current Scope
These pages cover the current sandbox-first setup flow:
npm install -g openclaw@latestopenclaw onboard --non-interactive- Discord or Feishu channel setup
- direct model-auth verification before channel testing
They do not yet describe a one-click product flow in Cue.