openclaw - 💡(How to fix) Fix [Bug] LCM plugin shows '(unconfigured)' briefly during startup [2 comments, 3 participants]

TL;DR

The LCM plugin should be modified to read the lossless-claw summaryModel config before announcing its status to avoid displaying "(unconfigured)" when a valid override exists.

Guidance

• Review the LCM plugin's initialization sequence to ensure it reads the external configuration before logging its status.
• Consider adding a delay or a synchronization mechanism to ensure the plugin has read the configuration before announcing its status.
• Verify the fix by checking the logs after restarting the gateway with the updated plugin.
• Test the plugin with different configuration scenarios to ensure it correctly handles various summarization models.

Example

No code snippet is provided as the issue does not include specific code details.

Notes

The suggested fix assumes that the issue is caused by a race condition between the plugin's initialization and the reading of the external configuration. The actual implementation details may vary depending on the plugin's codebase.

Recommendation

Apply a workaround by modifying the LCM plugin to read the lossless-claw summaryModel config before announcing its status, as this approach directly addresses the identified race condition and should resolve the issue.