| name | openclaw-config-editor |
| description | Safely update OpenClaw instance configuration in openclaw.json files. Use this skill when the orchestrator needs to inspect or modify gateway settings for one or more OpenClaw agents.
|
| homepage | https://docs.openclaw.ai/gateway/configuration |
OpenClaw Config Editor
This skill enables the orchestrator to update openclaw.json files for local
OpenClaw instances in a controlled, repeatable way.
Reference
Always use the latest gateway configuration documentation as the source of
truth before making changes:
https://docs.openclaw.ai/gateway/configuration
Scope
Use this skill for editing instance config files such as:
/compose-files/configs/<agent-name>/openclaw.json
/mounted-agents/<agent-name>/.openclaw/openclaw.json (live runtime config)
For agents that are already running or previously initialized, update the live
runtime config at /mounted-agents/<agent-name>/.openclaw/openclaw.json.
Changes in /compose-files/configs/<agent-name>/openclaw.json are seed inputs
and are typically only copied on first initialization when no live config
exists.
Safety rules
- Read the current file before editing.
- Make the smallest valid change needed for the request.
- Preserve existing keys and formatting style where possible.
- Do not invent undocumented fields or values.
- Do not write secrets into config if they should come from environment variables.
- If a setting is unclear, check docs first and ask for clarification.
Workflow
- Identify target instance(s) and whether each one is already initialized/running.
- For initialized/running agents, treat
/mounted-agents/<agent-name>/.openclaw/openclaw.json as the source of truth and edit that file.
- Update
/compose-files/configs/<agent-name>/openclaw.json only when requested for seed consistency or future reprovisioning.
- Read current
openclaw.json for each target file before editing.
- Validate requested fields/shape against:
https://docs.openclaw.ai/gateway/configuration
- Apply minimal edits.
- Re-open and verify JSON validity and expected values.
- After live config changes, run gateway restart in the matching container:
docker exec openclaw-<agent-name> openclaw gateway restart
- Confirm restart command success from command output.
- Report exactly which files were changed and which were intentionally left unchanged.
Output checklist
Before handoff, confirm: