openclaw - 💡(How to fix) Fix Bug: Plugin checker prefers resolved runtime snapshot over source config snapshot [1 comments, 2 participants]

TL;DR

The issue can be fixed by modifying the readFacadeBoundaryConfigSafely() function to prefer the source config snapshot over the resolved runtime snapshot.

Guidance

• Verify that the openclaw.json file contains a fully-populated plugins.allow list to ensure the issue is not due to a configuration error.
• Patch the readFacadeBoundaryConfigSafely() function to call getRuntimeConfigSourceSnapshot() before getRuntimeConfigSnapshot() as a temporary workaround.
• To permanently fix the issue, update the src/plugin-sdk/facade-activation-check.runtime.ts file to swap the snapshot preference order, checking the source snapshot first.
• Test the fix by running Doctor, Gateway startup plugin loading, and OpenClaw install availability to ensure the plugin activation boundary checks are working correctly.

Example

// Before
function readFacadeBoundaryConfigSafely() {
  const runtimeSnapshot = getRuntimeConfigSnapshot();
  const sourceSnapshot = getRuntimeConfigSourceSnapshot();
  // ...
}

// After
function readFacadeBoundaryConfigSafely() {
  const sourceSnapshot = getRuntimeConfigSourceSnapshot();
  const runtimeSnapshot = getRuntimeConfigSnapshot();
  // ...
}

Notes

This fix assumes that the issue is solely due to the order of snapshot preference in the readFacadeBoundaryConfigSafely() function. If other factors are contributing to the issue, additional debugging may be necessary.

Recommendation

Apply the workaround by patching the readFacadeBoundaryConfigSafely() function, and then update the src/plugin-sdk/facade-activation-check.runtime.ts file to permanently fix the issue. This approach ensures that the plugin activation boundary checks are working correctly while minimizing potential disruptions.