2. 询问

1. “我应该在哪里部署它？” — Docker（本地或远程 SSH）还是裸机？
2. “名称？” — 用于容器。如果用户不在意，则生成一个。
3. “有什么特殊要求吗？” — 目的、约束。可选。

不要询问密钥、插件、技能、端口或配置。继承所有内容，使用默认值。

如果用户提供频道令牌（Telegram 机器人、Discord 机器人等），也一并设置。频道是可选的 — 不要主动询问，但如果提供则接受。

3. 确认计划

收集答案后，在执行任何操作之前展示完整计划。在一个摘要中显示所有内容：

计划如下：

📦 部署方式：在 <target> 上使用 Docker
📛 名称：<agent-name>
🌐 端口：<port>

从当前代理继承：
  ✅ 提供商：Anthropic (API 密钥)
  ✅ 模型：anthropic/claude-sonnet-4-20250514
  ✅ Brave Search API 密钥
  ✅ 插件：openclaw-agent-reach
  ✅ 技能：agent-spawner, weather
  ✅ 心跳间隔：30m

新代理将在收到第一条消息时引导建立其自身身份。

可以开始了吗？

仅列出实际存在的项目。在继续之前等待明确的确认。如果用户想要更改，进行调整并重新确认。

4. 部署

Docker

git clone https://github.com/openclaw/openclaw.git <agent-name>
cd <agent-name>

设置环境变量并运行非交互式引导。匹配步骤 1 中检测到的提供商：

首先检查端口冲突：

docker ps --format '{{.Ports}}' | grep -oP '\d+(?=->)' | sort -n

选择一个未使用的网关端口和桥接端口（按惯例，桥接端口 = 网关端口 + 1）。

export OPENCLAW_IMAGE=alpine/openclaw:latest
export OPENCLAW_CONFIG_DIR=~/.openclaw-<agent-name>
export OPENCLAW_WORKSPACE_DIR=~/.openclaw-<agent-name>/workspace
export OPENCLAW_GATEWAY_PORT=<unused port>
export OPENCLAW_BRIDGE_PORT=<unused port, typically gateway + 1>
export OPENCLAW_GATEWAY_BIND=lan

mkdir -p $OPENCLAW_CONFIG_DIR/workspace

引导标志因提供商而异。 使用匹配的 --auth-choice 和密钥标志：

docker compose run --rm openclaw-cli onboard --non-interactive --accept-risk \
  --mode local \
  --auth-choice <detected> \
  --<provider>-api-key "$API_KEY" \
  --gateway-port 18789 \
  --gateway-bind lan \
  --skip-skills

docker compose up -d openclaw-gateway

官方 compose 使用绑定挂载 — 主机用户拥有文件，没有权限问题。

引导时关于网关连接的错误是预期的（尚未运行）。配置已写入。

裸机

curl -fsSL https://openclaw.ai/install.sh | bash -s -- --no-onboard

openclaw onboard --non-interactive --accept-risk \
  --mode local \
  --auth-choice <detected> \
  --<provider>-api-key "$API_KEY" \
  --gateway-port 18789 \
  --gateway-bind lan \
  --install-daemon \
  --daemon-runtime node \
  --skip-skills

5. 修补运行中的代理

CLI 别名：

• Docker：OC="docker compose exec openclaw-gateway node /app/openclaw.mjs"
• 裸机：OC="openclaw"

配置（仅修补当前代理实际拥有的内容）：

$OC config set agents.defaults.model "<model>"
$OC config set agents.defaults.heartbeat.every "30m"
# 工具密钥 — 仅当它们存在于当前配置中时
$OC config set tools.web.search.apiKey "<key>"

插件（来自当前配置中的 plugins.installs）：

$OC plugins install <npm-spec>
# 对每个插件重复此操作

技能（从当前代理复制非捆绑技能）：

# Docker — 源技能在你的容器内，使用 docker cp
docker cp <your-container>:/home/node/.openclaw/workspace/skills/ /tmp/skills-transfer/
docker cp /tmp/skills-transfer/ <new-container>:/home/node/.openclaw/workspace/skills/
# 或者，如果远程部署，首先使用 scp 将它们复制到目标主机

# 裸机
cp -r <source-workspace>/skills/ ~/.openclaw/workspace/skills/

重启：

docker compose restart openclaw-gateway  # Docker
openclaw gateway restart                 # 裸机

6. 交接

读取网关令牌：

grep -A1 '"token"' $OPENCLAW_CONFIG_DIR/openclaw.json

告知用户：

• URL： http://<host>:<port>/
• 令牌： （来自配置 — 引导过程自动生成一个）
• “打个招呼 — 它会自行引导建立身份。”

注意事项

• Docker 内部 openclaw 不在 PATH 中。使用 node /app/openclaw.mjs。
• 非交互式引导需要 --accept-risk。
• alpine/openclaw:latest — 预构建的官方镜像。
• 不要使用命名的 Docker 卷 — 存在 root 所有权问题。官方 compose 使用绑定挂载。
• 同一主机上的多个代理：使用不同的 OPENCLAW_CONFIG_DIR、OPENCLAW_GATEWAY_PORT 和 OPENCLAW_BRIDGE_PORT。在部署前检查 docker ps 以查看已使用的端口。
• 插件和技能持久保存在 ~/.openclaw/ 卷中（extensions/ 和 workspace/skills/）。
• SSH 密钥、git 配置、apt 包是临时的 — 根据设计，不在卷中。

每周安装数

1

仓库

austineral/agent-spawner

首次出现

1 天前

安全审计

Gen Agent Trust HubFailSocketFailSnykFail

安装于

amp1

cline1

openclaw1

opencode1

cursor1

kimi-cli1

2. Ask

1. "Where should I deploy it?" — Docker (local or remote SSH) or bare metal?
2. "Name?" — for container. Generate one if they don't care.
3. "Anything special?" — purpose, constraints. Optional.

Don't ask about keys, plugins, skills, ports, or config. Carry everything over, use defaults.

If the user provides channel tokens (Telegram bot, Discord bot, etc.), set those up too. Channels are optional — don't ask, but accept if offered.

3. Confirm Plan

After gathering answers, present the full plan before doing anything. Show everything in one summary:

Here's the plan:

📦 Deploy: Docker on <target>
📛 Name: <agent-name>
🌐 Port: <port>

Carrying over from current agent:
  ✅ Provider: Anthropic (API key)
  ✅ Model: anthropic/claude-sonnet-4-20250514
  ✅ Brave Search API key
  ✅ Plugins: openclaw-agent-reach
  ✅ Skills: agent-spawner, weather
  ✅ Heartbeat: 30m

The new agent will bootstrap its own identity on first message.

Good to go?

Only list items that actually exist. Wait for explicit confirmation before proceeding. If the user wants changes, adjust and re-confirm.

4. Deploy

Docker

git clone https://github.com/openclaw/openclaw.git <agent-name>
cd <agent-name>

Set env and run non-interactive onboard. Match the provider detected in step 1:

Check for port conflicts first:

docker ps --format '{{.Ports}}' | grep -oP '\d+(?=->)' | sort -n

Pick a gateway port AND bridge port that aren't in use (bridge = gateway + 1 by convention).

export OPENCLAW_IMAGE=alpine/openclaw:latest
export OPENCLAW_CONFIG_DIR=~/.openclaw-<agent-name>
export OPENCLAW_WORKSPACE_DIR=~/.openclaw-<agent-name>/workspace
export OPENCLAW_GATEWAY_PORT=<unused port>
export OPENCLAW_BRIDGE_PORT=<unused port, typically gateway + 1>
export OPENCLAW_GATEWAY_BIND=lan

mkdir -p $OPENCLAW_CONFIG_DIR/workspace

Onboard flags vary by provider. Use the matching --auth-choice and key flag:

docker compose run --rm openclaw-cli onboard --non-interactive --accept-risk \
  --mode local \
  --auth-choice <detected> \
  --<provider>-api-key "$API_KEY" \
  --gateway-port 18789 \
  --gateway-bind lan \
  --skip-skills

docker compose up -d openclaw-gateway

Official compose uses bind mounts — host user owns files, no permission issues.

Onboard error about gateway connection is expected (not running yet). Config is written.

Bare metal

curl -fsSL https://openclaw.ai/install.sh | bash -s -- --no-onboard

openclaw onboard --non-interactive --accept-risk \
  --mode local \
  --auth-choice <detected> \
  --<provider>-api-key "$API_KEY" \
  --gateway-port 18789 \
  --gateway-bind lan \
  --install-daemon \
  --daemon-runtime node \
  --skip-skills

5. Patch Running Agent

CLI alias:

• Docker: OC="docker compose exec openclaw-gateway node /app/openclaw.mjs"
• Bare metal: OC="openclaw"

Config (only patch what the current agent actually has):

$OC config set agents.defaults.model "<model>"
$OC config set agents.defaults.heartbeat.every "30m"
# Tool keys — only if they exist in current config
$OC config set tools.web.search.apiKey "<key>"

Plugins (from plugins.installs in current config):

$OC plugins install <npm-spec>
# Repeat for each plugin

Skills (copy non-bundled skills from current agent):

# Docker — source skills are inside your container, use docker cp
docker cp <your-container>:/home/node/.openclaw/workspace/skills/ /tmp/skills-transfer/
docker cp /tmp/skills-transfer/ <new-container>:/home/node/.openclaw/workspace/skills/
# Or if deploying remotely, scp them to the target host first

# Bare metal
cp -r <source-workspace>/skills/ ~/.openclaw/workspace/skills/

Restart:

docker compose restart openclaw-gateway  # Docker
openclaw gateway restart                 # bare metal

6. Hand Off

Read the gateway token:

grep -A1 '"token"' $OPENCLAW_CONFIG_DIR/openclaw.json

Tell the user:

• URL: http://<host>:<port>/
• Token: (from config — onboard auto-generates one)
• "Say hello — it'll bootstrap itself."

Notes

• openclaw not in PATH inside Docker. Use node /app/openclaw.mjs.
• --accept-risk required for non-interactive onboard.
• alpine/openclaw:latest — pre-built official image.
• Don't use named Docker volumes — root ownership issues. Official compose uses bind mounts.
• Multiple agents on same host: use different OPENCLAW_CONFIG_DIR, OPENCLAW_GATEWAY_PORT, AND OPENCLAW_BRIDGE_PORT. Check docker ps for used ports before deploying.
• Plugins and skills persist in ~/.openclaw/ volume (extensions/ and workspace/skills/).
• SSH keys, git config, apt packages are ephemeral — not in the volume, by design.

Weekly Installs

1

Repository

austineral/agent-spawner

First Seen

1 day ago

Security Audits

Gen Agent Trust HubFailSocketFailSnykFail

Installed on

amp1

cline1

openclaw1

opencode1

cursor1

kimi-cli1