openclaw - 💡(How to fix) Fix Doctor cannot recover from invalid third-party plugin config; gateway hard-fails to start [1 participants]

• Plugin manifest/schema/runtime has incompatibility (e.g. missing required fields, schema format mismatch, runtime init error)

TL;DR

Implement a plugin preflight stage to quarantine incompatible plugins and enhance the openclaw doctor command to detect and remove broken plugin references.

Guidance

• Introduce a non-fatal isolation mechanism for non-core plugins to prevent startup failures due to incompatible plugins.
• Develop a quarantine list to store incompatible plugins and boot the gateway with warnings instead of failures.
• Enhance the openclaw doctor --fix command to detect and remove broken plugin references, including plugins.allow, plugins.entries, and plugins.load.paths.
• Consider adding a --safe-mode startup option or a doctor plugin quarantine command to facilitate outage recovery.

Example

No code snippet is provided as the issue does not contain specific code references.

Notes

The proposed solution focuses on improving the robustness of the OpenClaw startup process and the openclaw doctor command. However, the implementation details may vary depending on the specific requirements and constraints of the OpenClaw system.

Recommendation

Apply workaround by implementing a plugin preflight stage and enhancing the openclaw doctor command, as this approach addresses the root cause of the issue and provides a more robust solution for handling incompatible plugins.