fix(docs): correct in-sandbox OpenClaw config path in runtime controls#5436
fix(docs): correct in-sandbox OpenClaw config path in runtime controls#5436harjothkhara wants to merge 1 commit into
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (2)
✅ Files skipped from review due to trivial changes (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughA single-character path correction in ChangesOpenClaw Config Path Fix and Regression Guard
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Suggested labels
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
The runtime-controls page told users the OpenClaw "runtime source of truth inside the sandbox" is /opt/nemoclaw/openclaw.json, but that directory holds the NemoClaw plugin (installed via "openclaw plugins install /opt/nemoclaw"), not the config. OpenClaw reads its config from /sandbox/.openclaw/openclaw.json -- the path the Dockerfile writes and that src/lib/channel-runtime-status.ts calls "the same file OpenClaw parses." The Hermes sibling row already uses the correct /sandbox/.hermes paths. Add a regression test asserting the corrected path, mirroring the docs repro-test pattern (test/repro-5088-best-practices-layers.test.ts). Signed-off-by: harjoth <harjoth.khara@gmail.com>
f9023ca to
6ca5e6b
Compare
|
✨ Thanks for the proposed fix correcting the OpenClaw runtime source of truth path from |
|
Closing this as superseded. The fix here — correcting the OpenClaw in-sandbox source-of-truth path from |
Summary
The Runtime Controls page tells users the OpenClaw "runtime source of truth inside the sandbox" is
/opt/nemoclaw/openclaw.json. That directory holds the NemoClaw plugin, not the agent config — so a user following the doc to inspect or reconcile config would look in the wrong place. OpenClaw reads its config from/sandbox/.openclaw/openclaw.json. This corrects the path.Related Issue
None — found during a documentation correctness sweep. (No tracking issue filed.)
Changes
docs/manage-sandboxes/runtime-controls.mdx: fix the OpenClaw "runtime source of truth" path from/opt/nemoclaw/openclaw.jsonto/sandbox/.openclaw/openclaw.json. The Hermes sibling row a few lines below already uses the correct/sandbox/.hermes/config.yaml+/sandbox/.hermes/.envpaths.test/repro-runtime-controls-config-path.test.ts: add a regression test asserting the corrected OpenClaw path (and the existing Hermes paths), mirroring the existing docs-regression pattern intest/repro-5088-best-practices-layers.test.ts.Evidence the corrected path is the real one:
Dockerfileinstalls the NemoClaw plugin at/opt/nemoclaw(openclaw plugins install /opt/nemoclaw) and writes the agent config to/sandbox/.openclaw/openclaw.json.src/lib/channel-runtime-status.tsreads/sandbox/.openclaw/openclaw.jsonand documents it as "the same file OpenClaw parses at startup."Type of Change
(One-word prose correction; plus an additive docs-regression guard test. No runtime code or code samples changed.)
Verification
npx prek run --from-ref main --to-ref HEADpassesnpm testpasses (broad runtime changes only)npm run docsbuilds without warnings (doc changes only)Notes: the new regression test passes (
vitest run test/repro-runtime-controls-config-path.test.ts→ 2 passed). The fullnpm testandnpm run docsboxes are left unchecked because this is a prose-only change with no link or structural impact; the targeted regression test is the proof.Signed-off-by: harjoth harjoth.khara@gmail.com
Summary by CodeRabbit
Documentation
/sandbox/.openclaw/openclaw.json) instead of the prior/opt/...location.Tests