Repository navigation
Conversation
OpenClaw 2026.9.x keeps a plugin found on plugins.load.paths disabled
until it is enabled with capability consent, and NemoClaw's restrictive
plugins.allow blocks it outright ("not in allowlist"). Found live on the
personal-assistant sandbox with OpenClaw 2026.9.2: the daily-briefing
bundle and its MCP servers were detected but never loaded.
After pointing OpenClaw at the bundle, run `plugins enable` for the
bundle (its plugin.json name) and each native plugin under plugins/;
this also adds them to an existing plugins.allow. Older releases load
the bundle anyway and may not know --accept-capabilities, so retry
without it. The verify failure now says why the bundle is not loaded.
Co-Authored-By: Claude
sauagarwa
force-pushed
the
fix/openclaw-enable-harness
branch
from
October 13, 2026 14:28
93fc557 to
1c9f80d
Compare
sauagarwa
added a commit
to sauagarwa/secure-agent-workspace
that referenced
this pull request
Oct 13, 2026
…rns-sandbox#98 into demo Brings current main into demo (including validatedpatterns-sandbox#101, the NemoClaw v0.0.133 images with OpenClaw 2026.9.2) and the installer fix from validatedpatterns-sandbox#98 (1c9f80d), so a later main -> demo merge has nothing to redo. Conflict: values-secret.yaml.template. Main (validatedpatterns-sandbox#93) removed the keycloak-users entry (no implicit demo users); kept that, and the demo's Slack and Gmail entries. Co-Authored-By: Claude
sauagarwa
added a commit
to sauagarwa/secure-agent-workspace
that referenced
this pull request
Oct 13, 2026
… off The personal assistant moves to ghcr.io/validatedpatterns-sandbox/ nemoclaw-sandbox:latest, which validatedpatterns-sandbox#101 builds from NemoClaw v0.0.133 with OpenClaw 2026.9.2: that release loads the bundle's plugin.json and mcp.json (2026.7.1 loaded only its skills), and validatedpatterns-sandbox#98 enables it. With the Slack provider attached, OpenClaw treats its own slack chat channel as configured, tries to install @openclaw/slack from npm at gateway startup (egress denied) and does not start; the UI answers 502. Found live. The provider is for the harness's governed reads, so the installer sets channels.slack.enabled false in every sandbox with a Slack provider, instead of allowing npm egress. The demo docs now mark both Tier 1 blockers (T1a, T1c) as resolved and describe the bundle as it is (plugin.json, mcp.json). Co-Authored-By: Claude
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
1 participant
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.
Enable the harness plugins in OpenClaw
#101 moved the NemoClaw sandbox image to v0.0.133, which ships OpenClaw 2026.9.2. On OpenClaw 2026.9.x, a harness bundle mounted at
/sandbox/harnessis found but never loaded, so verification fails for any NemoClaw sandbox with a harness:openclaw plugins inspectgives the reason:"status": "disabled","activationReason": "not in allowlist". 2026.9.x keeps a plugin found onplugins.load.pathsdisabled until it is enabled with capability consent. The NemoClaw image also ships a restrictiveplugins.allow(brave,memory-core,nemoclaw), which blocks it outright. 2026.7.1 loaded the bundle regardless.Change
plugins.load.paths, the installer runsopenclaw plugins enable <id> --accept-capabilitiesfor the bundle (thenamein itsplugin.json) and for each native plugin underplugins/. On an administrator enable, OpenClaw also adds the id to an existingplugins.allow.--accept-capabilities, so the installer retries without it. Both steps are best effort; verification still decides.status disabled: not in allowlist).Checks
test_full_apply_mounts_the_harness_into_notebooknow also checks thatds-defaultand itssaw-echoplugin are enabled.daily-briefingharness, the bundle loads withslack-readerandgmail-readerregistered, the apply ends withapply: Done, and the assistant lists both tools.Notes
notebookuses the AIPCC OpenClaw image, andcuda-sandbox(NemoClaw) is disabled and has no harness. The demo's personal assistant (NemoClaw with thedaily-briefingharness) needs this before it moves to a v0.0.133 image.After this merges, I'll merge main into
demoso the demo branch has it too.