1.nodejs下载
# nodejs和npm
apt update
apt install -y nodejs npm
root@test-VMware-Virtual-Platform:/data# npm --version
9.2.0
root@test-VMware-Virtual-Platform:/data# node --version
v22.22.1
2.安装openclaw
npm i -g openclaw
3.配置openclaw
openclaw onboard
root@test-VMware-Virtual-Platform:/home/test# openclaw onboard🦞 OpenClaw 2026.5.12 (f066dd2) — One CLI to rule them all, and one more restart because you changed the port.▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
██░▄▄▄░██░▄▄░██░▄▄▄██░▀██░██░▄▄▀██░████░▄▄▀██░███░██
██░███░██░▀▀░██░▄▄▄██░█░█░██░█████░████░▀▀░██░█░█░██
██░▀▀▀░██░█████░▀▀▀██░██▄░██░▀▀▄██░▀▀░█░██░██▄▀▄▀▄██
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀🦞 OPENCLAW 🦞 ┌ OpenClaw setup
│
◇ Security disclaimer ──────────────────────────────────────────────────────────────────────╮
│ │
│ OpenClaw is a hobby project and still in beta. Expect sharp edges. │
│ By default, OpenClaw is a personal agent: one trusted operator boundary. │
│ This bot can read files and run actions if tools are enabled. │
│ A bad prompt can trick it into doing unsafe things. │
│ │
│ OpenClaw is not a hostile multi-tenant boundary by default. │
│ If multiple users can message one tool-enabled agent, they share that delegated tool │
│ authority. │
│ │
│ If you’re not comfortable with security hardening and access control, don’t run │
│ OpenClaw. │
│ Ask someone experienced to help before enabling tools or exposing it to the internet. │
│ │
│ Recommended baseline │
│ - Pairing/allowlists + mention gating. │
│ - Multi-user/shared inbox: split trust boundaries (separate gateway/credentials, ideally │
│ separate OS users/hosts). │
│ - Sandbox + least-privilege tools. │
│ - Shared inboxes: isolate DM sessions (session.dmScope: per-channel-peer) and keep tool │
│ access minimal. │
│ - Keep secrets out of the agent’s reachable filesystem. │
│ - Use the strongest available model for any bot with tools or untrusted inboxes. │
│ │
│ Run regularly │
│ openclaw security audit --deep │
│ openclaw security audit --fix │
│ │
│ Learn more │
│ - https://docs.openclaw.ai/gateway/security │
│ │
├────────────────────────────────────────────────────────────────────────────────────────────╯
│
◇ I understand this is personal-by-default and shared/multi-user use requires lock-down. Continue?
│ Yes
│
◇ Setup mode
│ QuickStart (recommended)
│
◇ QuickStart ─────────────────────────╮
│ │
│ Gateway port: 18789 │
│ Gateway bind: Loopback (127.0.0.1) │
│ Gateway auth: Token (default) │
│ Tailscale exposure: Off │
│ Direct to chat channels. │
│ │
├──────────────────────────────────────╯
│
◇ Model/auth provider
│ More…
│
◇ Model/auth provider
│ DeepSeek
│
◇ Enter DeepSeek API key
│ ▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪▪
│
◇ Model configured ────────────────────────────────╮
│ │
│ Default model set to deepseek/deepseek-v4-flash │
│ │
├───────────────────────────────────────────────────╯
│
◇ Default model
│ Browse all models
│
│
◇ Default model
│ Keep current (deepseek/deepseek-v4-flash)
│
◇ How channels work ───────────────────────────────────────────────────────────────────────╮
│ │
│ Inbound DM safety defaults to pairing: unknown senders get a pairing code first. │
│ Approve with: openclaw pairing approve <channel> <code> │
│ Open/public DMs require dmPolicy="open" plus allowFrom=["*"]. │
│ For multi-user DMs, isolate sessions with: openclaw config set session.dmScope │
│ "per-channel-peer" (or "per-account-channel-peer" for multi-account channels). │
│ Docs: channels/pairing │
│ │
│ Feishu: 飞书/Lark enterprise messaging with doc/wiki/drive tools. │
│ WeCom: Enterprise messaging and documents, scheduling, task tools. │
│ Google Chat: Google Workspace Chat app with HTTP webhook. │
│ Nostr: Decentralized protocol; encrypted DMs via NIP-04. │
│ Microsoft Teams: Teams SDK; enterprise support. │
│ Mattermost: self-hosted Slack-style chat; install the plugin to enable. │
│ Nextcloud Talk: Self-hosted chat via Nextcloud Talk webhook bots. │
│ Matrix: open protocol; install the plugin to enable. │
│ LINE: LINE Messaging API webhook bot. │
│ Weixin: Personal WeChat messaging via QR-code login. │
│ Zalo: Vietnam-focused messaging platform with Bot API. │
│ ClickClack: self-hosted chat via first-class ClickClack bot tokens. │
│ Yuanbao: Tencent Yuanbao AI assistant conversation channel. │
│ Zalo Personal: Zalo personal account via QR code login. │
│ Synology Chat: Connect your Synology NAS Chat to OpenClaw with full agent capabilities. │
│ Tlon: decentralized messaging on Urbit; install the plugin to enable. │
│ Discord: very well supported right now. │
│ iMessage: Local iMessage/SMS through the imsg bridge, including private API message │
│ actions when enabled. │
│ IRC: classic IRC networks with DM/channel routing and pairing controls. │
│ QQ Bot: connect to QQ via official QQ Bot API with group chat and direct message │
│ support. │
│ Signal: signal-cli linked device; more setup (David Reagans: "Hop on Discord."). │
│ Slack: supported (Socket Mode). │
│ Telegram: simplest way to get started — register a bot with @BotFather and get going. │
│ Twitch: Twitch chat integration │
│ WhatsApp: works with your own number; recommend a separate phone + eSIM. │
│ │
├───────────────────────────────────────────────────────────────────────────────────────────╯
│
◇ Select channel (QuickStart)
│ Feishu/Lark (飞书)
│
◇ Installed Feishu plugin
│
◇ How do you want to connect Feishu?
│ Scan a QR code to create a bot automatically
│
◇ Which Feishu domain?
│ Feishu (feishu.cn) - China
│
◇ Feishu scan-to-create ───────────────────────────────────────────────────────────────╮
│ │
│ Scan the QR with Lark/Feishu on your phone. If the mobile app does not react, rerun │
│ setup and choose manual input. │
│ │
├───────────────────────────────────────────────────────────────────────────────────────╯# 这里会生成一个二维码，使用飞书手机端app扫描就可以自动创建或者使用现有的机器人
│
◇ Scan completed.
│
◇ Group chat policy
│ Open - respond in all groups (requires mention)
│
◇ Bot configured.
[info]: [ 'client ready' ]
│
◇ Selected channels ─────────────────────────────────────╮
│ │
│ Feishu — 飞书/Lark enterprise messaging. Docs: feishu │
│ │
├─────────────────────────────────────────────────────────╯
Updated ~/.openclaw/openclaw.json
Workspace OK: ~/.openclaw/workspace
Sessions OK: ~/.openclaw/agents/main/sessions
│
◇ Web search ─────────────────────────────────────────────────────────────────╮
│ │
│ Web search lets your agent look things up online. │
│ Choose a provider. Some providers need an API key, and some work key-free. │
│ Docs: https://docs.openclaw.ai/tools/web │
│ │
├──────────────────────────────────────────────────────────────────────────────╯
│
◇ Search provider
│ DuckDuckGo Search (experimental)
│
◇ Web search ──────────────────────────────────────────────────────────────╮
│ │
│ DuckDuckGo Search (experimental) works without an API key. │
│ OpenClaw will enable the plugin and use it as your web_search provider. │
│ Docs: https://docs.openclaw.ai/tools/web │
│ │
├───────────────────────────────────────────────────────────────────────────╯
│
◇ Skills status ─────────────╮
│ │
│ Eligible: 11 │
│ Missing requirements: 38 │
│ Unsupported on this OS: 7 │
│ Blocked by allowlist: 0 │
│ │
├─────────────────────────────╯
│
◇ Configure skills now? (recommended)
│ No
│
◇ Hooks ──────────────────────────────────────────────────────────────────╮
│ │
│ Hooks let you automate actions when agent commands are issued. │
│ Example: Save session context to memory when you issue /new or /reset. │
│ │
│ Learn more: https://docs.openclaw.ai/automation/hooks │
│ │
├──────────────────────────────────────────────────────────────────────────╯
│
◇ Enable hooks?
│ Skip for now
Config overwrite: /root/.openclaw/openclaw.json (sha256 bd67cbc42d7f67b0c87f84b1fd986349738aeadcb8cbffb99f51dbe654ce6795 -> fa12e880ec61be0374e229e5ce16f482f24266fd74989e06e7be28ae25e6c6fe, backup=/root/.openclaw/openclaw.json.bak)
│
◇ Gateway service runtime ────────────────────────────────────────────╮
│ │
│ QuickStart uses Node for the Gateway service (stable + supported). │
│ │
├──────────────────────────────────────────────────────────────────────╯
│
◇ Gateway service install failed.
│
◇ Gateway ──────────────────────────────────────────────────────────────────────────────╮
│ │
│ Gateway service install failed: systemctl enable failed: Failed to enable unit: Unit │
│ openclaw-gateway.service does not exist │
│ │
├────────────────────────────────────────────────────────────────────────────────────────╯
│
◇ Gateway ───────────────────────────────────────────────────────╮
│ │
│ Tip: rerun `openclaw gateway install` after fixing the error. │
│ │
├─────────────────────────────────────────────────────────────────╯
Health check failed: connect ECONNREFUSED 127.0.0.1:18789
│
◇ Health check help ────────────────────────────────╮
│ │
│ Docs: │
│ https://docs.openclaw.ai/gateway/health │
│ https://docs.openclaw.ai/gateway/troubleshooting │
│ │
├────────────────────────────────────────────────────╯
│
◇ Optional apps ────────────────────────╮
│ │
│ Add nodes for extra features: │
│ - macOS app (system + notifications) │
│ - iOS app (camera/canvas) │
│ - Android app (camera/canvas) │
│ │
├────────────────────────────────────────╯
│
◇ Control UI ─────────────────────────────────────────────────────────────────────╮
│ │
│ Web UI: http://127.0.0.1:18789/ │
│ Web UI (with token): │
│ http://127.0.0.1:18789/#token=2e04fafef6c2c9ad13194477c936048feb7d2bd7722b25b0 │
│ Gateway WS: ws://127.0.0.1:18789 │
│ Gateway: not detected (connect ECONNREFUSED 127.0.0.1:18789) │
│ Docs: https://docs.openclaw.ai/web/control-ui │
│ │
├──────────────────────────────────────────────────────────────────────────────────╯
│
◇ Hatch your agent ───────────────────────────────────────────────────╮
│ │
│ Your workspace is ready. │
│ The first Terminal chat run will send: "Wake up, my friend!" │
│ Edit BOOTSTRAP.md later to change how the agent introduces itself. │
│ │
├──────────────────────────────────────────────────────────────────────╯
│
◇ How do you want to hatch your agent?
│ Hatch later
│
◇ Later ───────────────────────────────────────────╮
│ │
│ When you're ready: openclaw dashboard --no-open │
│ │
├───────────────────────────────────────────────────╯
│
◇ Workspace backup ────────────────────────────────────────╮
│ │
│ Back up your agent workspace. │
│ Docs: https://docs.openclaw.ai/concepts/agent-workspace │
│ │
├───────────────────────────────────────────────────────────╯
│
◇ Security ──────────────────────────────────────────────────────╮
│ │
│ Running agents on your computer is risky — harden your setup: │
│ https://docs.openclaw.ai/security │
│ │
├─────────────────────────────────────────────────────────────────╯
│
◇ Web search ──────────────────────────────────────────────────────────────────────╮
│ │
│ Provider DuckDuckGo Search (experimental) is selected but no API key was found. │
│ web_search will not work until a key is added. │
│ openclaw configure --section web │
│ │
│ Get your key at: https://duckduckgo.com/ │
│ Docs: https://docs.openclaw.ai/tools/web │
│ │
├───────────────────────────────────────────────────────────────────────────────────╯
│
◇ What now ─────────────────────────────────────────────────────────────╮
│ │
│ What now: https://openclaw.ai/showcase ("What People Are Building"). │
│ │
├────────────────────────────────────────────────────────────────────────╯
│
└ Onboarding complete. Use the dashboard link above to control OpenClaw.
4.启动openclaw
- 此时只能通过飞书app或者本地web ui的方式连接openclaw，如果想局域网内连接看下列步骤
openclaw gateway run
- 第一次连接时，需要再openclaw.json中获取gateway.token进行认证登录
# 参考token
cat /root/.openclaw/openclaw.json | grep -w \"token | tail -1
http://127.0.0.1:18789
5.设置局域网内连接openclaw web ui
# 第一步：允许局域网访问
openclaw config set gateway.bind lan
作用：将网关从 loopback（仅本地）模式切换为 lan（局域网/公网可访问）模式# 第二步：允许非安全认证（解决 origin 限制的关键）
openclaw config set gateway.controlUi.allowInsecureAuth true# 第三步：（可选）禁用设备认证
openclaw config set gateway.controlUi.dangerouslyDisableDeviceAuth true
注意：此步骤会降低安全性，仅在可信局域网内使用# 第四步：获取本机局域网 IP（自行获取）# 第五步：配置允许的来源 Origins（解决跨域访问）
openclaw config set 'gateway.controlUi.allowedOrigins' '["http://192.168.11.20:18789"]'
将 192.168.11.20 替换为你实际的局域网 IP 地址
http://192.168.11.20:18789
6.遇到的问题
- openclaw通过openclaw onboard配置小米的models时，默认是按量付费的接口地址，如果你使用的是小米的token plan，那么配置完启动openclaw后会报错401，需要手动修改openclaw.json配置文件进行添加
[diagnostic] lane task error: lane=main durationMs=2566 error="FailoverError: HTTP 401: Invalid API Key"
- 我在openclaw.json配置文件中手动添加小米token plan后（https://token-plan-cn.xiaomimimo.com/v1）,报错opencalw使用tools，小米mimo模型无法解析，但是我发送的信息“”你好“”或者“”hi“”也不行，目前无法解决
- hermes是可以配置的
[diagnostic] lane task error: lane=session:agent:main:feishu:direct:ou_624a7650d456b0b026af00c8913d60a0f durationMs=757 error="FailoverError: LLM request failed: provider rejected the request schema or tool payload."
[model-fallback/decision] model fallback decision: decision=candidate_failed requested=test123/mimo-v2.5 candidate=test123/mimo-v2.5 reason=format next=none detail=400 Param Incorrect
7.openclaw官网地址
https://openclaw.ai/
