docs: refresh config schema mirror refs

This commit is contained in:
Peter Steinberger
2026-04-04 20:38:15 +01:00
parent 420f2191f5
commit 0ef29325ed
2 changed files with 6 additions and 5 deletions

View File

@@ -1602,7 +1602,7 @@ for usage/billing and raise limits as needed.
- Use `openclaw config set` for small changes.
- Use `openclaw configure` for interactive edits.
- Use `config.schema.lookup` first when you are not sure about an exact path or field shape.
- Use `config.schema.lookup` first when you are not sure about an exact path or field shape; it returns a shallow schema node plus immediate child summaries for drill-down.
- Use `config.patch` for partial RPC edits; keep `config.apply` for full-config replacement only.
Docs: [Config](/cli/config), [Configure](/cli/configure), [Doctor](/gateway/doctor).
@@ -1775,7 +1775,7 @@ for usage/billing and raise limits as needed.
<Accordion title="Is there an API / RPC way to apply config?">
Yes.
- `config.schema.lookup`: inspect one config subtree with field docs before writing
- `config.schema.lookup`: inspect one config subtree with its shallow schema fields, matched UI hint, and immediate child summaries before writing
- `config.get`: fetch the current snapshot + hash
- `config.patch`: safe partial update (preferred for most RPC edits)
- `config.apply`: validate + replace the full config, then restart
@@ -2200,7 +2200,7 @@ for usage/billing and raise limits as needed.
- edit `agents.defaults.model` in `~/.openclaw/openclaw.json`
Avoid `config.apply` with a partial object unless you intend to replace the whole config.
For RPC edits, inspect with `config.schema.lookup` first and prefer `config.patch`
For RPC edits, inspect with `config.schema.lookup` first and prefer `config.patch`. The lookup payload gives you the normalized path, shallow schema docs/constraints, and immediate child summaries.
for partial updates.
If you did overwrite config, restore from backup or re-run `openclaw doctor` to repair.