openclaw-complete-deployment-guide▌
nathansteelqoder/openclaw-config-qoder-integration · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
覆盖阿里云百炼模型配置、飞书 / 钉钉(传统机器人 + DEAP 高级方案)/ QQ / Discord 全平台接入、Qoder CLI 集成,以及高级配置与运维。
在阿里云上部署 OpenClaw 完整指南
覆盖阿里云百炼模型配置、飞书 / 钉钉(传统机器人 + DEAP 高级方案)/ QQ / Discord 全平台接入、Qoder CLI 集成,以及高级配置与运维。
⚠️ 安全警告
在开始之前,请务必阅读以下注意事项:
- 切勿在个人主力电脑上部署 OpenClaw——它具有高文件系统和命令执行权限
- 务必使用云服务器(如阿里云 ECS)进行部署,与本地环境隔离
- 保护好你的 API 密钥——使用环境变量或安全保险箱,不要硬编码在代码中
- 使用强随机令牌限制 Gateway 访问,避免使用简单密码
- 定期轮换凭证——特别是钉钉/飞书/QQ 等平台的应用密钥
使用场景
- 在阿里云 ECS 服务器上从零部署 OpenClaw AI 助手
- 通过钉钉(Stream 机器人或 DEAP 高级方案)与 AI 对话
- 通过飞书、QQ 或 Discord 接入 OpenClaw
- 配置阿里云百炼 Coding Plan 作为 AI 推理后端
- 将 Qoder CLI 注册为 ACP Agent,实现钉钉/飞书中的代码开发
示例
# 安装 OpenClaw
curl -fsSL https://clawd.bot/install.sh | bash
# 启动 Gateway
openclaw gateway --port 18789 --verbose
# 交互式配置模型和渠道
openclaw onboard
# 查看所有渠道状态
openclaw channel list
# 查看实时日志
tail -f /tmp/openclaw-gateway.log
注意事项
- 切勿在本地主力电脑部署,务必使用云服务器(如阿里云 ECS)
- 钉钉应用必须完成「版本发布」流程,仅保存配置不生效
- 钉钉 Client Secret、百炼 API Key、QQ 机器人密钥均只显示一次,需立即保存
- 飞书集成需选择「WebSocket 长连接」模式,不要使用 HTTP 回调
- 钉钉 DEAP 方案需在同一服务器运行 Connector,确保 18789 端口本地可访问
- 建议为 Gateway 配置随机强令牌认证(
openssl rand -hex 24)
概述
本指南将带你完成一套完整的 OpenClaw 云端部署,实现通过多种 IM 平台与 AI 助手对话,并可选接入 Qoder CLI 进行代码开发。
整体架构:
┌────────────────────────────────────────────────────────────┐
│ 用户层 │
│ ┌────────┐ ┌────────┐ ┌──────┐ ┌─────────┐ │
│ │ 飞书 │ │ 钉钉 │ │ QQ │ │ Discord │ │
│ └───┬────┘ └───┬────┘ └──┬───┘ └────┬────┘ │
└──────┼───────────┼──────────┼───────────┼─────────────────┘
│ │ │ │
└───────────┴──────────┴───────────┘
│
Stream / WebSocket
│
┌─────────────────────────────▼──────────────────────────────┐
│ OpenClaw Gateway :18789 │
│ ┌──────────────────────────────────────────────────────┐ │
│ │ ACP 协议层 │ │
│ │ ┌──────────┐ ┌──────────┐ ┌──────────┐ │ │
│ │ │ acpx │ │ 调度器 │ │ 会话管理 │ │ │
│ │ └──────────┘ └──────────┘ └──────────┘ │ │
│ └──────────────────────────────────────────────────────┘ │
│ ┌──────────────────────────────────────────────────────┐ │
│ │ 渠道连接器层(飞书 / 钉钉 / QQ / Discord) │ │
│ └──────────────────────────────────────────────────────┘ │
└─────────────────────────────────────────────────────────────┘
│
阿里云百炼 API / Qoder CLI
部署步骤总览:
- 购买并配置阿里云 ECS 服务器
- 安装 Node.js 与 OpenClaw
- 配置阿里云百炼模型(Coding Plan)
- 配置 Gateway 外部访问与认证
- 配置 ACP 协议支持
- 安装并配置 Qoder CLI(可选)
- 接入 IM 平台(飞书 / 钉钉 / QQ / Discord)
前置要求
必需账号和权限
- 阿里云账号
- 阿里云百炼账号(用于模型 API)
- 目标 IM 平台的开发者/管理员账号
必需软件(本地)
- SSH 客户端
- 现代浏览器(用于访问各平台开发者控制台)
第一阶段:阿里云服务器购买与配置
1.1 推荐服务器配置
| 配置项 | 最低要求 | 推荐配置 |
|---|---|---|
| CPU | 2 核 | 2 核 |
| 内存 | 2 GiB | 4 GiB |
| 磁盘 | 20 GB SSD | 40 GB ESSD |
| 带宽 | 1 Mbps | 20 Mbps+ |
| 操作系统 | Ubuntu 22.04 / CentOS 8 | Alibaba Cloud Linux 3 |
| 地域 | 任意 | 美国弗吉尼亚 / 中国香港(访问 AI 服务延迟低) |
1.2 购买方式
方式一:通过计算巢快速部署(推荐新手)
访问阿里云计算巢,一键部署预配置环境:
按页面指引:选择地域 → 选择实例规格 → 配置网络和安全组 → 确认创建。
方式二:手动购买 ECS 实例
- 访问 阿里云 ECS 控制台
- 点击「创建实例」
- 关键选项:
- 镜像:Alibaba Cloud Linux 3 / Ubuntu 22.04(如有 OpenClaw 应用镜像可直接选用)
- 实例规格:
ecs.c7.large(2 核 4 GiB)或更高 - 系统盘:40 GB ESSD
- 公网 IP:分配公网 IPv4
- 带宽:按使用流量或按固定带宽(至少 1 Mbps)
- 配置安全组(见下方)
- 设置登录凭证(密钥对推荐)
- 确认并创建
1.3 配置安全组规则
| 端口 | 协议 | 用途 | 授权对象 |
|---|---|---|---|
| 22 | TCP | SSH 远程连接 | 你的 IP 地址 |
| 18789 | TCP | OpenClaw Gateway | 0.0.0.0/0 |
配置步骤:
- ECS 控制台 → 找到实例 → 点击「安全组」
- 「配置规则」→「入方向」→「手动添加」以上规则
1.4 连接到服务器
# 使用密码登录
ssh root@<你的服务器公网IP>
# 使用密钥登录
ssh -i /path/to/your-key.pem root@<你的服务器公网IP>
# 或通过阿里云控制台网页终端:
# ECS 控制台 → 实例详情 → 远程连接
第二阶段:安装 Node.js 与 OpenClaw
2.1 安装 Node.js(推荐 nvm)
# 安装 nvm
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.7/install.sh | bash
source ~/.bashrc
# 安装 Node.js 22 LTS
nvm install 22
nvm use 22
node -v # 验证:应输出 v22.x.x
2.2 安装 OpenClaw
方式一:通过官方安装脚本(推荐)
curl -fsSL https://clawd.bot/install.sh | bash
方式二:通过 npm 全局安装
npm install -g openclaw
验证安装:
openclaw --version
# 预期输出:版本号如 "2026.1.x"
# 若提示命令不存在,尝试旧名称:clawdbot --version
2.3 启动 OpenClaw Gateway
# 方式一:前台启动(调试用)
openclaw gateway --port 18789 --verbose
# 方式二:后台启动
nohup setsid openclaw gateway --port 18789 --verbose > /tmp/openclaw-gateway.log 2>&1 &
# 检查状态
systemctl --user status openclaw-gateway.service
# 或
openclaw gateway status
第三阶段:配置阿里云百炼模型(Coding Plan)
3.1 购买 Coding Plan 套餐
| 套餐 | 首月价格 | 次月价格 | 每月请求量 |
|---|---|---|---|
| Lite 基础版 | 7.9 元 | 40 元/月 | 18,000 次 |
| Pro 高级版 | 39.9 元 | 200 元/月 | 90,000 次 |
- 访问 阿里云百炼控制台
- 导航至「Coding Plan」或「订阅套餐」
- 选择 Lite 或 Pro 完成支付
3.2 获取 API 凭证
- Base URL(固定):
https://coding.dashscope.aliyuncs.com/v1 - API Key 格式:
sk-sp-xxxxx
获取步骤:
- 登录 阿里云百炼控制台
- 进入「密钥管理」或「API Keys」
- 点击「创建 API Key」
- 立即复制并保存——关闭后无法再次查看
支持的模型:
qwen3.5-plus- 通用场景(推荐入门)qwen3-max-2026-01-23- 高级推理kimi-k2.5- 代码生成(如可用)glm-5- 中文优化
3.3 配置 OpenClaw 使用百炼
方式一:交互式引导
openclaw onboard
按提示操作:
- 选择「添加自定义模型供应商」
- 供应商 ID:
bailian - Base URL:
https://coding.dashscope.aliyuncs.com/v1 - API Key:粘贴
sk-sp-xxxxx - API 类型:
openai-completions - 添加模型:
qwen3.5-plus - 设为默认模型
方式二:手动编辑配置文件
编辑 ~/.openclaw/openclaw.json:
{
"models": {
"providers": {
"bailian": {
"baseUrl": "https://coding.dashscope.aliyuncs.com/v1",
"apiKey": "sk-sp-YOUR_KEY_HERE",
"api": "openai-completions",
"models": [
{
"id": "qwen3.5-plus",
"name": "Qwen 3.5 Plus",
"reasoning": true,
"input": ["text"],
"contextWindow": 32000,
"maxTokens": 4096
}
]
}
}
},
"agents": {
"defaults": {
"model": {
"primary": "bailian/qwen3.5-plus"
}
}
}
}
第四阶段:配置 Gateway 外部访问与认证
当需要通过钉钉 DEAP 或其他外部服务访问 Gateway 时,需配置认证和 HTTP 端点。
4.1 生成强认证令牌
openssl rand -hex 24
# 示例输出:a3f7c2e1d4b5a6c7d8e9f0a1b2c3d4e5f6a7b8c9d0e1f2a3
4.2 更新 Gateway 配置
编辑 ~/.openclaw/openclaw.json,添加 gateway 部分:
{
"gateway": {
"port": 18789,
"mode": "local",
"bind": "loopback",
"controlUI": {
"allowInsecureAuth": false
},
"auth": {
"mode": "token",
"token": "在此处填入上一步生成的强令牌"
},
"http": {
"endpoints": {
"chatCompletions": {
"enabled": true
}
}
}
}
}
4.3 重启 Gateway
openclaw gateway restart
# 或手动重启:
pkill -f "openclaw gateway"
nohup setsid openclaw gateway --port 18789 --verbose > /tmp/openclaw-gateway.log 2>&1 &
4.4 验证 Gateway 正常运行
curl http://127.0.0.1:18789/health
# 应返回 {"status":"ok"} 或类似响应
第五阶段:配置 ACP 协议支持
ACP(Agent Client Protocol)协议允许 OpenClaw 调度多种 AI Agent。
5.1 安装并启用 ACPX 插件
# 安装 ACPX 插件
openclaw plugins install @openclaw/acpx
# 启用插件
openclaw config set plugins.entries.acpx.enabled true
5.2 配置 ACP 参数
# 启用 ACP
openclaw config set acp.enabled true
# 启用 ACP 调度
openclaw config set acp.dispatch.enabled true
# 设置后端为 acpx
openclaw config set acp.backend "acpx"
how to use openclaw-complete-deployment-guideHow to use openclaw-complete-deployment-guide on Cursor
AI-first code editor with Composer
1Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add openclaw-complete-deployment-guide
2Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
$npx skills add https://github.com/nathansteelqoder/openclaw-config-qoder-integration --skill openclaw-complete-deployment-guideThe skills CLI fetches openclaw-complete-deployment-guide from GitHub repository nathansteelqoder/openclaw-config-qoder-integration and configures it for Cursor.
3Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
◆ Which agents do you want to install to?││ ── Universal (.agents/skills) ── always included ────│ • Amp│ • Antigravity│ • Cline│ • Codex│ ●Cursor(selected)│ • Cursor│ • Windsurf4Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/openclaw-complete-deployment-guideReload or restart Cursor to activate openclaw-complete-deployment-guide. Access the skill through slash commands (e.g., /openclaw-complete-deployment-guide) or your agent's skill management interface.
⚠Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
Additional Resources
List & Monetize Your Skill
Submit your Claude Code skill and start earning
GET_STARTED →Use Cases▌
Task Automation & Efficiency
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
✓Save 3-5 hours per week on routine tasks
Knowledge Enhancement
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
✓Accelerate learning and skill development by 2x
Quality Improvement
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
✓Improve work quality by 30-40% with less effort
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client with skill support
- ›Clear understanding of task or problem to solve
- ›Willingness to iterate and refine outputs
Time Estimate
15-45 minutes depending on use case complexity
Installation Steps
- 1.Install skill using provided installation command
- 2.Test with simple use case relevant to your work
- 3.Evaluate output quality and relevance
- 4.Iterate on prompts to improve results
- 5.Integrate into regular workflow if valuable
Common Pitfalls
- ⚠Expecting perfect results without iteration
- ⚠Not providing enough context in prompts
- ⚠Using skill for tasks outside its intended scope
- ⚠Accepting outputs without review and validation
Best Practices▌
✓ Do
- +Start with clear, specific prompts
- +Provide relevant context and constraints
- +Review and refine all outputs before using
- +Iterate to improve output quality
- +Document successful prompt patterns
✗ Don't
- −Don't use without understanding skill limitations
- −Don't skip validation of outputs
- −Don't share sensitive information in prompts
- −Don't expect skill to replace human judgment
💡 Pro Tips
- ★Be specific about desired format and style
- ★Ask for multiple options to choose from
- ★Request explanations to understand reasoning
- ★Combine AI efficiency with human expertise
When to Use This▌
✓ Use When
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid When
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
Learning Path▌
- 1Familiarize yourself with skill capabilities and limitations
- 2Start with low-risk, non-critical tasks
- 3Progress to more complex and valuable use cases
- 4Build expertise through regular use and experimentation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
general reviewsRatings
4.5★★★★★36 reviews- ★★★★★Isabella Thompson· Dec 28, 2024
openclaw-complete-deployment-guide reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Chaitanya Patil· Dec 12, 2024
openclaw-complete-deployment-guide is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Zara Zhang· Dec 4, 2024
openclaw-complete-deployment-guide fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Zaid Brown· Nov 23, 2024
I recommend openclaw-complete-deployment-guide for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Yusuf Patel· Nov 19, 2024
Registry listing for openclaw-complete-deployment-guide matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Piyush G· Nov 3, 2024
Keeps context tight: openclaw-complete-deployment-guide is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Shikha Mishra· Oct 22, 2024
openclaw-complete-deployment-guide has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Zaid Agarwal· Oct 14, 2024
openclaw-complete-deployment-guide reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Layla Thompson· Oct 10, 2024
openclaw-complete-deployment-guide fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Arya Brown· Sep 9, 2024
openclaw-complete-deployment-guide reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 36
1 / 4