菜单
Switch a Worker Agent's LLM model via hiclaw CLI. Use when the human admin requests changing a Worker's model.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | worker-model-switch |
| description | Switch a Worker Agent's LLM model via hiclaw CLI. Use when the human admin requests changing a Worker's model. |
Switch a Worker's LLM model using the hiclaw CLI. The controller handles all details: model parameter resolution, openclaw.json generation, storage push, and container recreation.
hiclaw update worker --name <WORKER_NAME> --model <MODEL_ID>
Examples:
hiclaw update worker --name alice --model claude-sonnet-4-6
hiclaw update worker --name alice --model deepseek-chat
The controller automatically:
spec.modelopenclaw.json and pushes it to storageYou do NOT need to specify context window, reasoning, or any model parameters — the controller knows them.
The CLI prints worker/<name> configured. The controller reconciles the change automatically. No manual restart is needed.
Report the CLI error output to the human admin. Common causes:
If the admin requests a model not in the controller's built-in registry, the controller uses safe defaults (contextWindow=150000, maxTokens=128000, reasoning=true, input=["text"]). If the admin needs specific parameters for an unknown model, they should update the controller's model registry rather than overriding at the skill level.
Analyze current OpenClaw setup and generate a migration package (ZIP) for importing into HiClaw as a managed Worker
Use before direct filesync calls, reading non-task shared files, pushing mid-task progress, or troubleshooting missing shared files. Do not use for normal task acceptance or submission; taskflow ack_task and submit_task handle lifecycle sync internally.
Discover and install agent skills from the open ecosystem. Use when you encounter an unfamiliar domain, framework, or workflow that you lack specialized knowledge about, or when your coordinator suggests searching for skills before starting a task.
Use only when you need to look up team topology, worker phase, runtime state, or identity that is NOT available from the current message context. Do not use for standard task flows — the coordinator is the message sender, and the task room is in meta.json.room_id.
Sync files with centralized storage. Use when your coordinator or another Worker notifies you of file updates (config changes, task files, shared data, collaboration artifacts).
Discover and install agent skills from the open ecosystem. Use when you encounter an unfamiliar domain, framework, or workflow that you lack specialized knowledge about, or when your coordinator suggests searching for skills before starting a task.