Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve. Reviewed June 13, 2026, 8:35 AM ET / 12:35 UTC.

Summary
Keep open: current main and the latest release both show CLI commands on /nodes, but the page does not include the direct openclaw.json example the reporter requested. The fix is a small docs-only clarification anchored to the existing config schema and safety wording.

Reproducibility: yes. Source inspection of docs/nodes/index.md on current main shows CLI config commands but no openclaw.json/JSON5 example on the reported page.

Next step
A single docs PR can address the missing example using existing schema/types and docs-reference sources.

Review details

Best possible solution:

Add a compact, source-backed JSON5 openclaw.json example on /nodes near the existing node exec and command-policy guidance, with a link to the full configuration reference.

Do we have a high-confidence way to reproduce the issue?

Yes. Source inspection of docs/nodes/index.md on current main shows CLI config commands but no openclaw.json/JSON5 example on the reported page.

Is this the best way to solve the issue?

Yes. The narrowest maintainable fix is a docs-only example that mirrors src/config/types.tools.ts and src/config/types.gateway.ts, rather than adding config behavior.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against 8eb1fa09c66e.

Label changes

Label changes:

add P3: This is a low-risk documentation clarity improvement for a specific page rather than a broken runtime workflow.
add issue-rating: 🦞 diamond lobster: Current issue advisory state selects this label.
add clawsweeper:source-repro: Current issue advisory state selects this label.
add clawsweeper:queueable-fix: Current issue advisory state selects this label.
add clawsweeper:fix-shape-clear: Current issue advisory state selects this label.

Label justifications:

P3: This is a low-risk documentation clarity improvement for a specific page rather than a broken runtime workflow.

Evidence reviewed

Acceptance criteria:

pnpm docs:list
pnpm docs:check-mdx
pnpm docs:check-links

What I checked:

Live issue context: The issue body says Page: /nodes and asks for an example for the openclaw.json; live GitHub has no linked fix PR and no protected labels.
Docs page gap on current main: The /nodes source has CLI openclaw config set commands for tools.exec.host, tools.exec.security, and tools.exec.node, but rg found no openclaw.json or json5 example on this page. Public docs: docs/nodes/index.md. (docs/nodes/index.md:159, 8eb1fa09c66e)
Canonical exec config shape: The config type confirms the direct JSON shape for node exec binding: tools.exec.host, tools.exec.security, tools.exec.ask, and tools.exec.node. (src/config/types.tools.ts:314, 8eb1fa09c66e)
Canonical gateway node config shape: The gateway config type and zod schema define gateway.nodes.pairing.autoApproveCidrs, gateway.nodes.allowCommands, and gateway.nodes.denyCommands, so any docs example should use those current keys. (src/config/types.gateway.ts:441, 8eb1fa09c66e)
Existing example is off-page: The full configuration reference already has a gateway.nodes example and field details, but the reported /nodes page only links/mentions the concepts rather than showing the requested local example. Public docs: docs/gateway/configuration-reference.md. (docs/gateway/configuration-reference.md:544, 8eb1fa09c66e)
Latest release check: The latest release tag has the same /nodes gap: CLI config commands are present, but openclaw.json/json5 is absent from docs/nodes/index.md; the config reference and CLI node page contain related examples elsewhere. (docs/nodes/index.md:159, 8c802aa68351)

Likely related people:

@vincentkoc: Current /nodes, config schema, and config reference files in this checkout blame to commit 991471b8..., merged from PR fix(providers): skip unreadable Mistral tool schemas #90242 authored by Vincent Koc. (role: recent docs/config contributor; confidence: high; commits: 991471b8ec29, 5ef8f566ebd7; files: docs/nodes/index.md, src/config/types.gateway.ts, src/config/zod-schema.ts)
@steipete: History shows many focused updates to docs/nodes/index.md, including node exec routing and pairing clarifications, and PR 90242 was merged by Peter Steinberger. (role: repeated node docs contributor; confidence: medium; commits: 45c8207ef29c, 848e7abb57b3, 991471b8ec29; files: docs/nodes/index.md, docs/cli/nodes.md)
Josh Avant: Commit 8e132aed... changed device pairing behavior and added corresponding docs/nodes/index.md guidance, making Josh a useful routing candidate for node-pairing docs accuracy. (role: adjacent node pairing contributor; confidence: medium; commits: 8e132aed6eea; files: docs/nodes/index.md, src/infra/device-pairing.ts)

How this review workflow works

ClawSweeper keeps one durable marker-backed review comment per issue or PR.
Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
Maintainers can also comment @clawsweeper review to request a fresh review only.
Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

Uh oh!

Docs feedback: /nodes #92662

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions