OpenClaw Model Switch & Rescue
ReviewAudited by ClawScan on May 10, 2026.
Overview
This is a disclosed administrator runbook for changing OpenClaw model settings and restarting services, but it uses powerful server and credential access that users should handle carefully.
Install only if you need an OpenClaw administrator runbook for model switching or node rescue. Before using it, verify the target server, use least-privilege access instead of root where possible, back up configuration files, and require confirmation before restarting services or deleting pairing state.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Using this skill may give the agent access to a central server and sensitive provider credentials if the user supplies them.
The skill requires a central server address, an SSH private key path, and a model API key, but these credentials are expected for the stated server/model rescue purpose and no artifact shows leakage or unrelated use.
| CENTRAL_IP | 中央服务器 IP | 从配置文件获取 |\n| SSH_KEY | SSH 私钥路径 | ~/.ssh/id_ed25519 |\n| API_KEY | 模型 API Key | 从平台获取 |
Use a least-privilege SSH account where possible, verify the target IP, avoid exposing API keys unnecessarily, and declare these variables in metadata for clearer user review.
A mistaken command could interrupt the OpenClaw gateway or apply the wrong model configuration.
The documented workflow modifies OpenClaw configuration and restarts or kills gateway processes. These are high-impact actions, but they are directly tied to the model-switching/rescue purpose and are openly documented.
sed -i 's/\"primary\": \"[^\"]*\"/\"primary\": \"gpt-4o-mini\"/' ~/.openclaw/openclaw.json\n...\nsudo systemctl restart openclaw-gateway\n...\npkill -f openclaw-gateway
Confirm the target host and intended model before running commands, keep the backup step, and prefer explicit user approval before service restarts or process kills.
Deleting the wrong pairing file or using the wrong gateway details could leave a node disconnected.
The node-pairing rescue step deletes local pairing state and restarts a node connection. This is expected for a pairing repair workflow, but it can disrupt node connectivity if used incorrectly.
rm ~/.openclaw/node.json\n\n# 重新启动节点\ncd ~/.openclaw\nnpx openclaw node run --host <gateway_ip> --port <gateway_port>
Back up node.json before deletion, verify gateway host and port, and run this only when repairing an intended node pairing.
Users may not see all prerequisites from registry metadata alone.
The registry metadata does not declare the environment variables or tools referenced in SKILL.md. This appears to be an under-declaration rather than hidden code, because the requirements are stated in the skill text.
Required env vars: none; Env var declarations: none; Required binaries: none; No install spec — this is an instruction-only skill.
Declare CENTRAL_IP, SSH_KEY, API_KEY, and expected command-line tools in metadata so users can review prerequisites before installing.