fix(cli): make channels add atomic when policy preset is missing#4577
Merged
Conversation
Signed-off-by: Tinson Lai <tinsonl@nvidia.com>
Contributor
📝 WalkthroughWalkthroughThe CLI now requires the channel's built-in network policy preset to load and validates parsed ChangesPreset Application Prerequisite for Channel Add
Estimated code review effort🎯 4 (Complex) | ⏱️ ~45 minutes Possibly related PRs
Suggested labels
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
Contributor
E2E Advisor RecommendationRequired E2E: Dispatch hint: Auto-dispatched E2E: Full advisor summaryE2E Recommendation AdvisorBase: Required E2E
Optional E2E
New E2E recommendations
Dispatch hint
|
Contributor
E2E Scenario Advisor RecommendationRequired scenario E2E: Dispatch required scenario E2E:
Full scenario advisor summaryE2E Scenario AdvisorBase: Required scenario E2E
Optional scenario E2E
Relevant changed files
|
Contributor
PR Review AdvisorFindings: 2 needs attention, 6 worth checking, 0 nice ideas Review findings🛠️ Needs attention
🔎 Worth checking
🌱 Nice ideas
Since last review detailsCurrent findings:
This is an automated advisory review. A human maintainer must make the final merge decision. |
Contributor
Selective E2E Results — ✅ All requested jobs passedRun: 26711436094
|
Signed-off-by: Tinson Lai <tinsonl@nvidia.com>
Contributor
|
🌿 Preview your docs: https://nvidia-preview-pr-4577.docs.buildwithfern.com/nemoclaw |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/manage-sandboxes/messaging-channels.mdx`:
- Around line 167-168: The two-sentence paragraph describing `channels add`
should be split so each sentence is on its own line and the em dash before the
remediation instruction should be replaced with a period; edit the block that
starts with "`channels add` requires the matching built-in network policy preset
YAML..." so the first sentence ends after "sandbox is never left advertising a
channel without a matching network policy." and the second sentence begins with
"If the file is present..." and ends after "rebuild prompt.", then convert the
em dash in the remediation sentence after "apply itself fails" into a period and
put "restore the preset YAML and re-run `nemoclaw <sandbox> channels add
<channel>`." on its own line.
In `@docs/reference/commands.mdx`:
- Line 726: The sentence in the docs line about NemoClaw packs multiple
sentences onto one line and uses an em dash; split that paragraph into separate
lines with one sentence per line and replace the em dash with a period, e.g.
break the long line starting with "NemoClaw requires..." into three separate
sentences/lines describing (1) missing preset YAML behavior, (2) behavior when
the file is present and apply occurs, and (3) recovery instruction starting with
"restore the preset YAML and re-run `nemoclaw <name> channels add <channel>`".
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Enterprise
Run ID: 0fd7308a-cb1a-4806-aa4d-dd5969adb849
📒 Files selected for processing (4)
docs/manage-sandboxes/messaging-channels.mdxdocs/reference/commands.mdxsrc/lib/actions/sandbox/policy-channel.tstest/channels-add-preset.test.ts
🚧 Files skipped from review as they are similar to previous changes (1)
- src/lib/actions/sandbox/policy-channel.ts
Contributor
Selective E2E Results — ✅ All requested jobs passedRun: 26711992585
|
… style Signed-off-by: Tinson Lai <tinsonl@nvidia.com>
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
docs/manage-sandboxes/messaging-channels.mdx (1)
168-170: 💤 Low valueConsider varying sentence structure to improve readability.
Three consecutive sentences begin with "If", creating a repetitive pattern. While grammatically correct, varying the structure would improve flow.
💡 Possible rewrite
-If the file is missing, the command exits with a non-zero status before any token prompt, registry write, or rebuild prompt, so the sandbox is never left advertising a channel without a matching network policy. -If the file is present, `channels add` applies the preset to the sandbox automatically before the rebuild so the bridge has egress to its upstream API. -If the apply itself fails, the command exits with a non-zero status without prompting for rebuild. +When the file is missing, the command exits with a non-zero status before any token prompt, registry write, or rebuild prompt, so the sandbox is never left advertising a channel without a matching network policy. +When the file is present, `channels add` applies the preset to the sandbox automatically before the rebuild so the bridge has egress to its upstream API. +Should the apply itself fail, the command exits with a non-zero status without prompting for rebuild.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/manage-sandboxes/messaging-channels.mdx` around lines 168 - 170, Reword the three consecutive sentences starting with "If" to vary sentence openings and improve flow: keep the same facts about the missing file (command exits non-zero before prompts so sandbox isn't left advertising a channel), the present file behavior (`channels add` auto-applies the preset before rebuild so bridge has egress), and the failed-apply behavior (command exits non-zero without prompting for rebuild), but change sentence structure — e.g., start one sentence with the consequence, another with the condition using a different phrasing, and the third as a dependent clause — updating the lines that contain "If the file is missing", "`channels add` applies", and "If the apply itself fails".
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/manage-sandboxes/messaging-channels.mdx`:
- Line 168: Rewrite the passive sentence in the given paragraph to active voice:
replace "so the sandbox is never left advertising a channel without a matching
network policy" with an active construction such as "so the command prevents the
sandbox from advertising a channel without a matching network policy." Update
the sentence that begins "If the file is missing, the command exits..." in the
messaging-channels.mdx content to use this active phrasing while preserving
meaning.
---
Nitpick comments:
In `@docs/manage-sandboxes/messaging-channels.mdx`:
- Around line 168-170: Reword the three consecutive sentences starting with "If"
to vary sentence openings and improve flow: keep the same facts about the
missing file (command exits non-zero before prompts so sandbox isn't left
advertising a channel), the present file behavior (`channels add` auto-applies
the preset before rebuild so bridge has egress), and the failed-apply behavior
(command exits non-zero without prompting for rebuild), but change sentence
structure — e.g., start one sentence with the consequence, another with the
condition using a different phrasing, and the third as a dependent clause —
updating the lines that contain "If the file is missing", "`channels add`
applies", and "If the apply itself fails".
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Enterprise
Run ID: 070d214f-3545-41cc-80ef-5431b1b49e8a
📒 Files selected for processing (4)
docs/manage-sandboxes/messaging-channels.mdxdocs/reference/commands.mdxsrc/lib/actions/sandbox/policy-channel.tstest/channels-add-preset.test.ts
🚧 Files skipped from review as they are similar to previous changes (2)
- src/lib/actions/sandbox/policy-channel.ts
- docs/reference/commands.mdx
…ay rollback Signed-off-by: Tinson Lai <tinsonl@nvidia.com>
Contributor
Selective E2E Results — ✅ All requested jobs passedRun: 26712645489
|
Contributor
There was a problem hiding this comment.
🧹 Nitpick comments (1)
docs/manage-sandboxes/messaging-channels.mdx (1)
170-170: ⚡ Quick winAdd article before "rebuild" for consistency.
The phrase "without prompting for rebuild" treats "rebuild" as an uncountable noun, but elsewhere in this document "rebuild" consistently takes an article as a countable noun: "the rebuild" (lines 169, 172, 177, 236, 238), "a manual rebuild" (line 184).
📝 Suggested fix
-When the apply step itself fails after the registry write, NemoClaw rolls back the bridge providers, the `messagingChannels` entry, and the persisted credentials, then exits without prompting for rebuild. +When the apply step itself fails after the registry write, NemoClaw rolls back the bridge providers, the `messagingChannels` entry, and the persisted credentials, then exits without prompting for a rebuild.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/manage-sandboxes/messaging-channels.mdx` at line 170, The sentence containing "without prompting for rebuild" should include the definite article to match the document's consistent usage; update that phrase to "without prompting for the rebuild" in the same sentence that starts "When the apply step itself fails after the registry write, NemoClaw rolls back the bridge providers, the `messagingChannels` entry, and the persisted credentials, then exits without prompting for rebuild" so it reads "...then exits without prompting for the rebuild."
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Nitpick comments:
In `@docs/manage-sandboxes/messaging-channels.mdx`:
- Line 170: The sentence containing "without prompting for rebuild" should
include the definite article to match the document's consistent usage; update
that phrase to "without prompting for the rebuild" in the same sentence that
starts "When the apply step itself fails after the registry write, NemoClaw
rolls back the bridge providers, the `messagingChannels` entry, and the
persisted credentials, then exits without prompting for rebuild" so it reads
"...then exits without prompting for the rebuild."
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Enterprise
Run ID: d82988eb-fc01-4d45-af25-0438299b37ab
📒 Files selected for processing (4)
docs/manage-sandboxes/messaging-channels.mdxdocs/reference/commands.mdxsrc/lib/actions/sandbox/policy-channel.tstest/channels-add-preset.test.ts
✅ Files skipped from review due to trivial changes (1)
- docs/reference/commands.mdx
🚧 Files skipped from review as they are similar to previous changes (2)
- src/lib/actions/sandbox/policy-channel.ts
- test/channels-add-preset.test.ts
Contributor
Selective E2E Results — ✅ All requested jobs passedRun: 26713016536
|
Signed-off-by: Tinson Lai <tinsonl@nvidia.com>
Contributor
Selective E2E Results — ✅ All requested jobs passedRun: 26713559497
|
…d re-add Signed-off-by: Tinson Lai <tinsonl@nvidia.com>
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
src/lib/actions/sandbox/policy-channel.ts (1)
810-828:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winMake
--dry-runhonor the new preset preflight.Right now
--dry-runreturns beforeloadPreset/parsePresetPolicyKeysrun, so it exits 0 even when the realchannels addwould now fail on a missing or malformed built-in preset. That makes the dry-run contract lie about whether the command is actually runnable.Suggested change
- if (dryRun) { - console.log(` --dry-run: would enable channel '${canonical}' for '${sandboxName}'.`); - return; - } - const presetContent = policies.loadPreset(canonical); const presetPolicyKeys = presetContent === null ? [] : policies.parsePresetPolicyKeys(presetContent); if (presetContent === null || presetPolicyKeys.length === 0) { if (presetContent !== null && presetPolicyKeys.length === 0) { console.error( ` Preset YAML for channel '${canonical}' has no parseable entries under 'network_policies:'.`, ); } console.error( ` Restore the preset YAML and re-run: ${CLI_NAME} ${sandboxName} channels add ${canonical}`, ); process.exit(1); } + + if (dryRun) { + console.log(` --dry-run: would enable channel '${canonical}' for '${sandboxName}'.`); + return; + }🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@src/lib/actions/sandbox/policy-channel.ts` around lines 810 - 828, The dry-run branch returns early and skips the new preset preflight, so dryRun in the channel add flow can report success even when policies.loadPreset(canonical) or policies.parsePresetPolicyKeys(...) would fail; modify the control flow in the function handling the --dry-run (check the dryRun variable) so that it still calls policies.loadPreset(canonical) and policies.parsePresetPolicyKeys(presetContent) and performs the same validation/error handling (including the console.error messages and process.exit(1) path using sandboxName, canonical, and CLI_NAME) but only skips the actual side-effect of enabling the channel—i.e., run the preset preflight before returning for dryRun.
🧹 Nitpick comments (1)
test/channels-add-preset.test.ts (1)
1374-1388: ⚡ Quick winValidate preset contents, not just file presence.
This guard still passes if
<channel>.yamlexists but is malformed or has no parseablenetwork_policies, which are the exact failure modesaddSandboxChannel()now treats as fatal. Parsing each on-disk preset here would make the source-of-truth test actually cover the new contract.♻️ Tighten the source-of-truth check
it("every channel registered in KNOWN_CHANNELS ships a matching preset YAML on disk", () => { const { knownChannelNames } = require(path.join(repoRoot, "dist", "lib", "sandbox", "channels.js")) as { knownChannelNames: () => string[]; }; + const { parsePresetPolicyKeys } = require(path.join(repoRoot, "dist", "lib", "policy", "index.js")) as { + parsePresetPolicyKeys: (content: string) => string[]; + }; const presetDir = path.join(repoRoot, "nemoclaw-blueprint", "policies", "presets"); const missing: string[] = []; for (const name of knownChannelNames()) { const file = path.join(presetDir, `${name}.yaml`); - if (!fs.existsSync(file)) missing.push(file); + if (!fs.existsSync(file)) { + missing.push(file); + continue; + } + const content = fs.readFileSync(file, "utf8"); + if (parsePresetPolicyKeys(content).length === 0) { + missing.push(`${file} (no parseable network_policies)`); + } } assert.deepEqual( missing, [], `every channel in KNOWN_CHANNELS must have a matching preset YAML; missing: ${missing.join(", ")}`,🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@test/channels-add-preset.test.ts` around lines 1374 - 1388, The test currently only checks that a preset file exists for each channel; instead, load and parse each YAML preset from presetDir for every name from knownChannelNames(), and assert that parsing succeeds and the resulting object contains a non-empty network_policies (or the exact key/shape addSandboxChannel() expects). Update the loop that builds missing to also read fs.readFileSync(file, "utf8"), parse with the same YAML loader used in production (or require the preset parser used by addSandboxChannel()), and push file onto missing (or a new failures list) if parsing throws or network_policies is absent/empty; finally assert failures is empty with a helpful message referencing addSandboxChannel()'s contract.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@src/lib/actions/sandbox/policy-channel.ts`:
- Around line 924-945: The rollback currently calls
onboardProviders.upsertMessagingProviders which can call process.exit on failure
and therefore prevents the registry restore; change this to a non-exiting,
best-effort provider-restore path (e.g. call a non-exiting variant like
onboardProviders.upsertMessagingProvidersBestEffort(...) or pass a { bestEffort:
true } flag to upsertMessagingProviders) inside a try/catch/finally so that any
gateway restore errors are caught and result in
residual.push("gateway-providers"), and ensure registry.updateSandbox(...) is
always executed (move it to finally or after the catch) so the prior registry
state is restored even when the gateway restore flakes.
---
Outside diff comments:
In `@src/lib/actions/sandbox/policy-channel.ts`:
- Around line 810-828: The dry-run branch returns early and skips the new preset
preflight, so dryRun in the channel add flow can report success even when
policies.loadPreset(canonical) or policies.parsePresetPolicyKeys(...) would
fail; modify the control flow in the function handling the --dry-run (check the
dryRun variable) so that it still calls policies.loadPreset(canonical) and
policies.parsePresetPolicyKeys(presetContent) and performs the same
validation/error handling (including the console.error messages and
process.exit(1) path using sandboxName, canonical, and CLI_NAME) but only skips
the actual side-effect of enabling the channel—i.e., run the preset preflight
before returning for dryRun.
---
Nitpick comments:
In `@test/channels-add-preset.test.ts`:
- Around line 1374-1388: The test currently only checks that a preset file
exists for each channel; instead, load and parse each YAML preset from presetDir
for every name from knownChannelNames(), and assert that parsing succeeds and
the resulting object contains a non-empty network_policies (or the exact
key/shape addSandboxChannel() expects). Update the loop that builds missing to
also read fs.readFileSync(file, "utf8"), parse with the same YAML loader used in
production (or require the preset parser used by addSandboxChannel()), and push
file onto missing (or a new failures list) if parsing throws or network_policies
is absent/empty; finally assert failures is empty with a helpful message
referencing addSandboxChannel()'s contract.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Enterprise
Run ID: 8e731a0f-5c07-40f2-adb2-85f42e707d2a
📒 Files selected for processing (5)
docs/manage-sandboxes/messaging-channels.mdxdocs/reference/commands.mdxsrc/lib/actions/sandbox/policy-channel.tssrc/lib/policy/index.tstest/channels-add-preset.test.ts
✅ Files skipped from review due to trivial changes (1)
- docs/manage-sandboxes/messaging-channels.mdx
🚧 Files skipped from review as they are similar to previous changes (1)
- docs/reference/commands.mdx
Contributor
Selective E2E Results — ✅ All requested jobs passedRun: 26714552896
|
…ilure safety Signed-off-by: Tinson Lai <tinsonl@nvidia.com>
Contributor
Selective E2E Results — ✅ All requested jobs passedRun: 26715309625
|
Signed-off-by: Tinson Lai <tinsonl@nvidia.com>
Contributor
Selective E2E Results — ✅ All requested jobs passedRun: 26715901484
|
Contributor
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
src/lib/actions/sandbox/policy-channel.ts (1)
950-972:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winOnly report
gateway-providersresiduals when the restore actually fails.This branch prepopulates
residualand prints the cleanup warning before the best-effort restore runs, so a successfulupsertMessagingProviders(..., { bestEffort: true })still returns{ ok: false, residual: ["gateway-providers"] }and tells the user to do manual cleanup unnecessarily.Suggested fix
- const residual: string[] = ["gateway-providers"]; - console.error( - ` ${YW}⚠${R} Rollback could not fully clean ${residual.join(", ")}; run '${CLI_NAME} ${sandboxName} channels remove ${canonical}' once the gateway is reachable.`, - ); + const residual: string[] = + Object.keys(snapshot.priorCreds).length > 0 ? [] : ["gateway-providers"]; if (Object.keys(snapshot.priorCreds).length > 0) { try { const priorTokenDefs = Object.entries(snapshot.priorCreds).map(([envKey, token]) => ({ name: bridgeProviderName(sandboxName, canonical, envKey), envKey, token, })); onboardProviders.upsertMessagingProviders(priorTokenDefs, runOpenshell, { bestEffort: true, }); } catch (err) { + if (!residual.includes("gateway-providers")) residual.push("gateway-providers"); console.error( ` ${YW}⚠${R} Failed to restore gateway providers for '${canonical}': ${ err instanceof Error ? err.message : String(err) }`, ); } } + if (residual.length > 0) { + console.error( + ` ${YW}⚠${R} Rollback could not fully clean ${residual.join(", ")}; run '${CLI_NAME} ${sandboxName} channels remove ${canonical}' once the gateway is reachable.`, + ); + } return { ok: false, residual };🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@src/lib/actions/sandbox/policy-channel.ts` around lines 950 - 972, The code prepopulates residual = ["gateway-providers"] and logs the cleanup warning before attempting the best-effort restore, causing false-positive residual reporting; change the flow so you only add "gateway-providers" to residual and emit the console.error/return it when the restore actually fails. Concretely, move initialization of residual to an empty array, run the upsertMessagingProviders call inside the try block (using snapshot.priorCreds -> priorTokenDefs built with bridgeProviderName(sandboxName, canonical, envKey)), and only push("gateway-providers") and log the CLI_NAME warning if upsertMessagingProviders throws (catch path) or if priorCreds is empty/unrestorable; keep runOpenshell and bestEffort usage unchanged.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Outside diff comments:
In `@src/lib/actions/sandbox/policy-channel.ts`:
- Around line 950-972: The code prepopulates residual = ["gateway-providers"]
and logs the cleanup warning before attempting the best-effort restore, causing
false-positive residual reporting; change the flow so you only add
"gateway-providers" to residual and emit the console.error/return it when the
restore actually fails. Concretely, move initialization of residual to an empty
array, run the upsertMessagingProviders call inside the try block (using
snapshot.priorCreds -> priorTokenDefs built with bridgeProviderName(sandboxName,
canonical, envKey)), and only push("gateway-providers") and log the CLI_NAME
warning if upsertMessagingProviders throws (catch path) or if priorCreds is
empty/unrestorable; keep runOpenshell and bestEffort usage unchanged.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Enterprise
Run ID: a977310f-b44f-4224-96b8-2b5610cde13b
📒 Files selected for processing (7)
docs/manage-sandboxes/messaging-channels.mdxdocs/reference/commands.mdxsrc/lib/actions/sandbox/policy-channel.tssrc/lib/onboard/providers.test.tssrc/lib/onboard/providers.tssrc/lib/policy/index.tstest/channels-add-preset.test.ts
✅ Files skipped from review due to trivial changes (1)
- docs/reference/commands.mdx
🚧 Files skipped from review as they are similar to previous changes (3)
- docs/manage-sandboxes/messaging-channels.mdx
- src/lib/policy/index.ts
- test/channels-add-preset.test.ts
cv
approved these changes
Jun 1, 2026
Contributor
Selective E2E Results — ❌ Some jobs failedRun: 26785074041
|
This was referenced Jun 2, 2026
wscurran
added
area: messaging
3 tasks
cv
pushed a commit
that referenced
this pull request
Jun 3, 2026
## Summary - Add the missing `v0.0.57` release-notes section with links to the detailed docs pages for command, inference, onboarding, messaging, status, installer, and policy changes. - Remove public references to docs-skip terms from source docs and regenerate the NemoClaw user skills from the current Fern MDX docs. - Carry forward generated references for the per-agent documentation split, including Hermes-specific reference files. ## Source summary - #4615 and #4653 -> `docs/about/release-notes.mdx`, `docs/reference/commands.mdx`: Release notes now cover host-side `sessions` and `agents` commands plus `NEMOCLAW_EXTRA_AGENTS_JSON` secondary-agent baking. - #4163, #4204, #4611, #4619, and #4676 -> `docs/about/release-notes.mdx`, `docs/inference/use-local-inference.mdx`: Release notes now cover managed vLLM progress/readiness, DGX Spark model default changes, local Ollama streaming usage, and inference route divergence warnings. - #4267, #4601, #4609, #4642, #4645, and #4661 -> `docs/about/release-notes.mdx`, `docs/reference/commands.mdx`: Release notes now cover UFW auto-remediation, local-inference reachability gates, gateway reuse/binding, cancel rollback, and policy selection persistence. - #4577, #4582, #4607, and #4660 -> `docs/about/release-notes.mdx`, `docs/manage-sandboxes/messaging-channels.mdx`: Release notes now cover Slack validation, atomic `channels add`, WhatsApp QR diagnostics, and Slack placeholder normalization. - #4388, #4600, #4646, and #4647 -> `docs/about/release-notes.mdx`, `docs/reference/commands.mdx`: Release notes now cover status failure layers, paused-container hints, Docker-driver doctor behavior, and non-destructive stale-registry recovery. - #4569, #4579, and #4678 -> `docs/about/release-notes.mdx`, `docs/manage-sandboxes/lifecycle.mdx`, `docs/network-policy/integration-policy-examples.mdx`: Release notes now cover installer tag pinning, PyPI `uv` policy access, and observable Jira validation. - #4632 -> `.agents/skills/`: Regenerated user skills from the current per-agent docs source, including newly generated Hermes reference files. ## Verification - `python3 scripts/docs-to-skills.py docs/ .agents/skills/ --prefix nemoclaw-user --doc-platform fern-mdx` - `rg "permissive mode|shields down|shields up|shields status|config rotate-token|rotate-token" docs --glob "*.mdx"` - `rg "permissive mode|shields down|shields up|shields status|config rotate-token|rotate-token" .agents/skills --glob "*.md"` - `npm run docs` - `npm run build:cli` - Commit hooks: markdownlint, docs-to-skills verification, gitleaks, skills YAML, commitlint <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Documentation** * Restructured documentation to clearly distinguish OpenClaw and Hermes agent variants throughout user guides. * Enhanced security, credential storage, and deployment guidance with clearer setup flows. * Added Hermes plugin installation and ecosystem documentation. * Improved workspace, messaging, and policy management references with variant-specific command examples. * Refined troubleshooting and CLI reference sections for clarity. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
nemoclaw <sandbox> channels add <channel>reachedprocess.exit(0)and wrote the channel intosandboxes.jsoneven when the matching policy preset YAML was missing on disk, leaving the sandbox advertising a bridge that had no network policy. The add flow now parses the preset YAML (file present andnetwork_policies:section yields at least one entry viaparsePresetPolicyKeys) before--dry-runreturns, before snapshotting registry/credentials state, and before token acquisition, and rolls back the gateway/registry/credential mutations when the post-write preset application fails. Rollback is best-effort: gateway-side steps that fail (provider detach/delete, or re-upsert during a re-add restore) print aRollback could not fully clean <surfaces>warning so the operator can clean up manually.Related Issue
Fixes #4548
Changes
addSandboxChannelruns thepolicies.loadPreset(canonical)+policies.parsePresetPolicyKeys(...)preflight before--dry-runreturns, before snapshotting registry/credentials state, and before token acquisition, so a missing, unloadable, or unparseable preset (no usable entries undernetwork_policies:) exits non-zero with a restore-and-re-run hint on stderr without prompting the operator or contacting the gateway.applyChannelAddToGatewayAndRegistry. On apply failure the newrollbackChannelAddhelper handles two cases. A fresh add clears credentials then callsapplyChannelRemoveToGatewayAndRegistry(best-effort, prints residual warning before returning). A failed re-add of an already-enabled channel restores the prior registry entry first (so a later gateway-upsert exit cannot orphan the channel), prints thegateway-providersresidual warning, then restores on-disk credentials and best-effort re-upserts the prior bridge providers.applyChannelRemoveToGatewayAndRegistrygrew an optional{ bestEffort: true }mode that downgrades each gateway-sideprocess.exit(1)to a log-and-continue so the registry rollback finishes even when openshell detach or delete fails; returns{ ok, residual }.applyChannelPresetIfAvailableno longer short-circuits viapolicies.listPresets(); the filesystem scan conflated "channel has no preset" with "preset file missing on disk", which is what let the original bug pass silently.docs/manage-sandboxes/messaging-channels.mdx,docs/reference/commands.mdx): describe the missing-or-unparseable-preset abort, the best-effort fresh-add rollback with explicit residual warning, the re-add restoration semantics, and narrow--dry-runto "validate channel name and matching policy preset without prompting for credentials, contacting the gateway, or rebuilding"; one sentence per line per docs style guide.test/channels-add-preset.test.ts: addedpresetFileMissing,presetMissingNetworkPolicies,presetMalformedYamlfixture toggles plus regression tests covering each abort/rollback path (missing YAML for both telegram and whatsapp/QR, missingnetwork_policies:section, malformed YAML body, applyPreset-after-write rollback, rollback resilience when openshell detach fails, prior-config restoration on a failed re-add, and registry restoration ordering when the re-upsert during re-add rollback itself throws); the source-of-truth test now parses every preset viaparsePresetPolicyKeysinstead of just checking file existence.Type of Change
Verification
npx prek run --all-filespassesnpm testpassesnpm run docsbuilds without warnings (doc changes only)Signed-off-by: Tinson Lai tinsonl@nvidia.com
Summary by CodeRabbit
New Features
Bug Fixes
Refactor
Documentation
Tests