## Release Range
- Previous release: `v0.0.110` at `9ab3cd3a569e6d01aef26dee876461d281aef06a`
- Candidate: `29c031c3813e41623df277442061f7961ea161e5`
- Commits: 68
- Risky files detected: 182
## QA Context
### Risky Areas
- Workflow / enforcement
- Credentials / inference
- Installer / bootstrap
- Sandbox / policy / SSRF
- Onboarding / host glue
### Suggested Test Focus
- Fresh install and upgrade paths
- Onboarding wizard and sandbox creation
- Policy enforcement, network egress, and SSRF protections
- CI checks, pre-commit hooks, and DCO declarations
- Credential storage and inference provider routing
## Canonical Release Entry
- Path: `docs/changelog/2026-08-18.mdx`
- Entry:
## v0.0.111
NemoClaw v0.0.111 extends the explicit experimental Portable profile with receipt-owned Hermes lifecycle authority and a fixed host-gateway and registry network topology.
It makes Shields recovery, sandbox rebuilds, provider routing, and messaging bootstrap more diagnosable and less likely to leave ambiguous state.
It also improves headless and local-inference onboarding, managed gateway recovery, uninstall cleanup, and release qualification.
- Experimental Portable Hermes onboarding now publishes `pending`, `configuring`, and `active` lifecycle receipts that bind the selected rootless Podman socket, exact container, startup command, policy, and registry identity.
An active receipt supports `launch`, `connect`, `recover`, `start`, `stop`, `status`, and read-only `doctor` without falling back to Docker; incomplete receipts direct operators to resume onboarding, and unsupported commands fail before effects.
Portable onboarding also keeps every agent off Docker-labeled recreation, requires the exact stopped container to reach its terminal `exited` state, accepts the managed Hermes startup command through the root helper, and settles receipt-owned Portable uninstall in one invocation.
The Portable network now configures `169.254.1.2/32` as the OpenShell host gateway and attaches the managed registry at the distinct `169.254.1.3` address.
For more information, refer to the [NemoHermes CLI Commands Reference](/user-guide/hermes/reference/commands), [Set Up an OpenAI-Compatible Endpoint](/user-guide/hermes/inference/custom-endpoints/set-up-openai-compatible-endpoint), and [Uninstall NemoClaw](/user-guide/hermes/manage-sandboxes/operate-sandboxes/uninstall-nemoclaw).
Related changes: [PR #9424](https://github.com/NVIDIA/NemoClaw/pull/9424), [PR #9447](https://github.com/NVIDIA/NemoClaw/pull/9447), [PR #9476](https://github.com/NVIDIA/NemoClaw/pull/9476), [PR #9509](https://github.com/NVIDIA/NemoClaw/pull/9509), [PR #9511](https://github.com/NVIDIA/NemoClaw/pull/9511), and [PR #9513](https://github.com/NVIDIA/NemoClaw/pull/9513).
- OpenClaw `connect` now reports a Shields auto-relock that occurs during the active terminal session, keeps the session open, and prints the exact host command to lower Shields again.
`backup-all` recovers lockdown from its trusted policy snapshot and stops before processing another sandbox when it cannot restore the prior Shields state.
Rebuild carries read-only host mounts into the recreate session and fails closed on an older journal that cannot prove the original host-mount identity.
OpenClaw rebuild also verifies the final `openclaw.json` and `.config-hash` pair, restores Shields, and exits nonzero when it cannot confirm config integrity.
Uninstall removes package-owned `nemoclaw`, `nemohermes`, and `nemo-deepagents` binaries and aliases installed under NVM, including binaries that point through a linked npm package, while preserving foreign entries and the linked package source.
Managed MCP credential reservations now make `credentials add --from-existing` fail before gateway mutation; operators can provide explicit credential keys or remove the reserving MCP servers.
For more information, refer to [Create and Restore Snapshots](/user-guide/openclaw/manage-sandboxes/state-and-backups/create-and-restore-snapshots), [Recover and Rebuild Sandboxes](/user-guide/openclaw/manage-sandboxes/operate-sandboxes/recover-and-rebuild-sandboxes), and the [NemoClaw CLI Commands Reference](/user-guide/openclaw/reference/commands).
Related changes: [PR #9508](https://github.com/NVIDIA/NemoClaw/pull/9508), [PR #9510](https://github.com/NVIDIA/NemoClaw/pull/9510), [PR #9471](https://github.com/NVIDIA/NemoClaw/pull/9471), [PR #9532](https://github.com/NVIDIA/NemoClaw/pull/9532), [PR #9502](https://github.com/NVIDIA/NemoClaw/pull/9502), and [PR #9546](https://github.com/NVIDIA/NemoClaw/pull/9546).
- Headless onboarding now warns before image pulls when Docker Desktop's `desktop` credential store is selected from a session where the helper is unavailable, and provides an isolated `DOCKER_CONFIG` recovery path.
Hermes Local Ollama validation distinguishes a daemon context setting from a model's native context cap and tells operators either to restart the daemon with the required value or select a larger model.
Windows-host Ollama discovery validates the response body and rejects non-object model entries, provider validation rejects replies whose only message field is null, and incomplete or converging OpenShell routes receive bounded, actionable diagnostics.
Deep Agents Code onboarding now accepts OpenRouter's native provider and model identity during fresh and resumed final validation instead of reporting false selection drift.
NemoClaw reports an OpenClaw-only `NEMOCLAW_OPENCLAW_OTEL*` variable as unsupported for Hermes or Deep Agents Code instead of reporting a missing Dockerfile `ARG`.
Station Express preserves the selected managed-vLLM provider state, onboarding traces record the flag that activated collection, and setup reports a dropped corporate CA import or a modified OpenShell migration instead of continuing with incomplete authority.
For more information, refer to [Use Ollama](/user-guide/hermes/inference/local-inference/set-up-ollama), [Configure Model Limits](/user-guide/hermes/inference/manage-inference/configure-model-limits), and [Troubleshooting](/user-guide/hermes/reference/troubleshooting).
Related changes: [PR #9459](https://github.com/NVIDIA/NemoClaw/pull/9459), [PR #9460](https://github.com/NVIDIA/NemoClaw/pull/9460), [PR #9482](https://github.com/NVIDIA/NemoClaw/pull/9482), [PR #9518](https://github.com/NVIDIA/NemoClaw/pull/9518), [PR #9488](https://github.com/NVIDIA/NemoClaw/pull/9488), [PR #9473](https://github.com/NVIDIA/NemoClaw/pull/9473), [PR #9481](https://github.com/NVIDIA/NemoClaw/pull/9481), [PR #9561](https://github.com/NVIDIA/NemoClaw/pull/9561), [PR #9507](https://github.com/NVIDIA/NemoClaw/pull/9507), [PR #9526](https://github.com/NVIDIA/NemoClaw/pull/9526), [PR #9516](https://github.com/NVIDIA/NemoClaw/pull/9516), [PR #9410](https://github.com/NVIDIA/NemoClaw/pull/9410), and [PR #9405](https://github.com/NVIDIA/NemoClaw/pull/9405).
- Managed messaging bootstrap now completes Discord setup, accepts reviewed per-agent credential placeholder aliases and the WeChat account token placeholder, and preserves the selected managed agent identity when onboarding reuses an existing sandbox.
The Open network-policy tier documentation also lists the experimental Microsoft Teams preset alongside the other messaging presets.
For more information, refer to [Enable Channels During Onboarding](/user-guide/openclaw/manage-sandboxes/messaging-channels/enable-channels-during-onboarding) and [Network Policies Reference](/user-guide/openclaw/reference/network-policies).
Related changes: [PR #9474](https://github.com/NVIDIA/NemoClaw/pull/9474), [PR #9477](https://github.com/NVIDIA/NemoClaw/pull/9477), [PR #9478](https://github.com/NVIDIA/NemoClaw/pull/9478), [PR #9479](https://github.com/NVIDIA/NemoClaw/pull/9479), and [PR #9504](https://github.com/NVIDIA/NemoClaw/pull/9504).
- Managed sandbox recovery now waits through exact bounded gateway startup states, stops downstream connect or launch work after a direct recovery failure, and preserves sanitized diagnostics when rollback or replacement identity cannot be confirmed.
Onboarding releases its temporary dashboard port reservation before the host forward starts, so the selected port remains available for that forward and later onboarding work.
Hermes GPU fallback rollback can restore the shared-state directory's setgid mode after ownership changes.
If restoration still fails, NemoClaw revalidates both container identities before removing only the transaction-owned replacement and leaving the original container stopped for cleanup.
Identity drift stops rollback without container mutation.
Docker replacement failures include the exact transaction-owned container identity, exit state, and a bounded redacted log tail, while the shared private-network boundary keeps inference and managed MCP target validation consistent.
New migration snapshots now use the canonical directory name and matching manifest identity so the documented list, prune, and delete retention commands can manage them.
Failed skill installation also removes its temporary SSH configuration, and NemoClaw recognizes the OpenShell `0.0.106` manifest contract used by the release.
For more information, refer to [Recover and Rebuild Sandboxes](/user-guide/openclaw/manage-sandboxes/operate-sandboxes/recover-and-rebuild-sandboxes), [Custom Endpoint Security](/user-guide/openclaw/inference/custom-endpoints/custom-endpoint-security), and [Troubleshooting](/user-guide/openclaw/reference/troubleshooting).
Related changes: [PR #9449](https://github.com/NVIDIA/NemoClaw/pull/9449), [PR #9480](https://github.com/NVIDIA/NemoClaw/pull/9480), [PR #9475](https://github.com/NVIDIA/NemoClaw/pull/9475), [PR #9569](https://github.com/NVIDIA/NemoClaw/pull/9569), [PR #9512](https://github.com/NVIDIA/NemoClaw/pull/9512), [PR #9445](https://github.com/NVIDIA/NemoClaw/pull/9445), [PR #9432](https://github.com/NVIDIA/NemoClaw/pull/9432), [PR #9434](https://github.com/NVIDIA/NemoClaw/pull/9434), and [PR #9224](https://github.com/NVIDIA/NemoClaw/pull/9224).
- Release and E2E automation now treats staging Launchable as advisory context, binds PR evidence to the shipped managed-image cohort, minimizes guard-chain evidence export, and aligns typed target titles and coverage inventory.
Provider-reservation contract coverage now verifies that a failed credential gateway mutation removes its provisional provider, while contributor automation limits each author to five concurrent PRs.
The contributor doctor accepts every Git boolean spelling that enables `commit.gpgsign` and continues to reject disabled, unset, or invalid values.
The cumulative documentation catch-up records the changed recovery, inference, Portable, policy, and troubleshooting contracts.
Related changes: [PR #9463](https://github.com/NVIDIA/NemoClaw/pull/9463), [PR #9469](https://github.com/NVIDIA/NemoClaw/pull/9469), [PR #9472](https://github.com/NVIDIA/NemoClaw/pull/9472), [PR #9484](https://github.com/NVIDIA/NemoClaw/pull/9484), [PR #9496](https://github.com/NVIDIA/NemoClaw/pull/9496), [PR #9498](https://github.com/NVIDIA/NemoClaw/pull/9498), [PR #9491](https://github.com/NVIDIA/NemoClaw/pull/9491), [PR #9514](https://github.com/NVIDIA/NemoClaw/pull/9514), [PR #9517](https://github.com/NVIDIA/NemoClaw/pull/9517), [PR #9536](https://github.com/NVIDIA/NemoClaw/pull/9536), [PR #9550](https://github.com/NVIDIA/NemoClaw/pull/9550), and [PR #9566](https://github.com/NVIDIA/NemoClaw/pull/9566).
## Pi Documentation Evidence
- Pi candidate: `29c031c3813e41623df277442061f7961ea161e5`
- Workflow: https://github.com/NVIDIA/NemoClaw/actions/runs/32252532844
- Attempt: 1
- Publish job: https://github.com/NVIDIA/NemoClaw/actions/runs/32252532844/job/96067996364
- Artifact: `post-merge-docs-approved`
- Review: `{"mainSha":"29c031c3813e41623df277442061f7961ea161e5","outcome":"approved","patchSha256":"e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855","repository":"NVIDIA/NemoClaw","version":1}`
- Managed candidate PR: absent.
- Managed candidate branch: absent.
## Base and Managed Image Evidence
- Base-image candidate: `29c031c3813e41623df277442061f7961ea161e5`
- Workflow: https://github.com/NVIDIA/NemoClaw/actions/runs/32252533527
- Attempt: 1
- `base-image-publication` job: https://github.com/NVIDIA/NemoClaw/actions/runs/32252533527/job/96066626058
## General E2E Decision
- Mode: Full manual `main` run.
- Selectors: Full suite.
- Release candidate: `29c031c3813e41623df277442061f7961ea161e5`.
- Tested commit: `dba453fd125d202fb4fbd84ff6df269034b798d1`.
- Candidate match: No.
- Workflow: https://github.com/NVIDIA/NemoClaw/actions/runs/32109622944
- Attempt: 1.
- Created: `2026-08-18T07:03:11Z`.
- Started: `2026-08-18T07:03:11Z`.
- Last updated: `2026-08-18T08:34:42Z`.
- Inspected: `2026-08-19T12:33:36Z`.
- Age at inspection: 1 day, 5 hours, 30 minutes, and 25 seconds.
- Workflow result: completed with failure.
- Release qualification: completed with failure from `2026-08-18T08:34:10Z` through `2026-08-18T08:34:17Z` at https://github.com/NVIDIA/NemoClaw/actions/runs/32109622944/job/95648791037.
- Failed jobs:
- `base-image-publication`: https://github.com/NVIDIA/NemoClaw/actions/runs/32109622944/job/95626046177
- `hermes-gpu-startup (fallback, e2e-hgpu-fallback, Fallback GPU startup reaches the stable Ready ro...)`: https://github.com/NVIDIA/NemoClaw/actions/runs/32109622944/job/95626383603
- `Exact staging Brev Launchable`: https://github.com/NVIDIA/NemoClaw/actions/runs/32109622944/job/95626384624
- `Messaging: adds and removes Telegram configuration / no provider credential`: https://github.com/NVIDIA/NemoClaw/actions/runs/32109622944/job/95626385679
- `Inference: rejects unsafe routes and proves runtime identities / no provider credential`: https://github.com/NVIDIA/NemoClaw/actions/runs/32109622944/job/95626385862
- `Snapshot: restores selected sandbox state without credential leaks / no provider credential`: https://github.com/NVIDIA/NemoClaw/actions/runs/32109622944/job/95626385899
- `Onboarding: reuses the gateway and preserves sibling sandboxes / no provider credential`: https://github.com/NVIDIA/NemoClaw/actions/runs/32109622944/job/95626386100
- `Networking: OpenClaw answers through balanced egress / Brave and NVIDIA inference API keys`: https://github.com/NVIDIA/NemoClaw/actions/runs/32109622944/job/95626386126
- `Search: OpenClaw returns a Brave result without exposing its key / Brave and NVIDIA inference API keys`: https://github.com/NVIDIA/NemoClaw/actions/runs/32109622944/job/95626386148
- `Gateway: restores the guard chain after recreation / NVIDIA inference API key`: https://github.com/NVIDIA/NemoClaw/actions/runs/32109622944/job/95626386548
- `OpenClaw: installs, onboards, and completes an agent turn / NVIDIA inference API key`: https://github.com/NVIDIA/NemoClaw/actions/runs/32109622944/job/95626386797
- `Security: OpenClaw retains the required sandbox posture / NVIDIA inference API key`: https://github.com/NVIDIA/NemoClaw/actions/runs/32109622944/job/95626386927
- Skipped jobs:
- `Compile protected llama.cpp DGX Spark plan`: https://github.com/NVIDIA/NemoClaw/actions/runs/32109622944/job/95626384087
- `retired-selector-compatibility`: https://github.com/NVIDIA/NemoClaw/actions/runs/32109622944/job/95626384092
- `native-runtime-qualification-producer-plan`: https://github.com/NVIDIA/NemoClaw/actions/runs/32109622944/job/95626384263
- `jetson-nvmap-gpu`: https://github.com/NVIDIA/NemoClaw/actions/runs/32109622944/job/95626384461
- `Build pinned native Podman toolchain / ${{ matrix.architecture }}`: https://github.com/NVIDIA/NemoClaw/actions/runs/32109622944/job/95626386999
- `Protected llama.cpp on NVIDIA DGX Spark`: https://github.com/NVIDIA/NemoClaw/actions/runs/32109622944/job/95626387434
- `matrix.jobName`: https://github.com/NVIDIA/NemoClaw/actions/runs/32109622944/job/95626391296
- `Aggregate native runtime qualification evidence`: https://github.com/NVIDIA/NemoClaw/actions/runs/32109622944/job/95626395816
- `live`: https://github.com/NVIDIA/NemoClaw/actions/runs/32109622944/job/95628219728
- `Relevant E2E`: https://github.com/NVIDIA/NemoClaw/actions/runs/32109622944/job/95648792390
- Cancelled, queued, or active jobs: None.
- Maintainer choice: Proceed with the status as shown.
Exceptions: The newest full E2E run failed and tested `dba453fd125d202fb4fbd84ff6df269034b798d1` instead of release candidate `29c031c3813e41623df277442061f7961ea161e5`; the maintainer is proceeding because general E2E is advisory for tag cutting, and the candidate's required documentation and base-image publication evidence passed.
