TL;DR

The issue can likely be resolved by modifying the dashboard to omit or restore redacted secret fields, such as gateway.remote.token, instead of submitting the redaction sentinel as literal config data.

Guidance

• Verify that the gateway.remote.token field is being redacted correctly in the dashboard and that the redaction sentinel __OPENCLAW_REDACTED__ is not being sent as real config input.
• Check the dashboard's configuration submission logic to ensure that it handles redacted fields properly and omits them from the submitted config data.
• Consider adding a validation step to prevent the submission of config data containing the redaction sentinel.
• Review the OpenClaw documentation for any specific guidelines on handling redacted secret fields in the dashboard.

Example

No code snippet is provided as the issue does not contain sufficient information about the specific code implementation.

Notes

The issue seems to be related to the dashboard's handling of redacted secret fields, and modifying the submission logic to omit or restore these fields should resolve the issue. However, without more information about the specific code implementation, it is difficult to provide a more detailed solution.

Recommendation

Apply workaround: Modify the dashboard to correctly handle redacted secret fields, such as gateway.remote.token, to prevent the submission of the redaction sentinel as literal config data. This should resolve the issue without requiring an upgrade to a fixed version.