openclaw - 💡(How to fix) Fix [Feature]: Expose messageId in message_sent plugin hook (toPluginMessageSentEvent) [1 participants]

Fix Plan

To fix the issue, we need to modify the toPluginMessageSentEvent function to include the messageId in the returned object. Here are the steps:

• Locate the toPluginMessageSentEvent function in the affected files (e.g., hook-runtime-*.js).
• Update the function to include the messageId property:

function toPluginMessageSentEvent(canonical) {
  return {
    to: canonical.to,
    content: canonical.content,
    success: canonical.success,
    messageId: canonical.messageId, // Add this line
  };
}

• Alternatively, you can use object destructuring and the spread operator to make the code more concise:

function toPluginMessageSentEvent({ to, content, success, messageId }) {
  return { to, content, success, messageId };
}

• Apply the changes to all affected files.

Verification

To verify that the fix worked, you can:

• Check the output of the toPluginMessageSentEvent function to ensure it includes the messageId property.
• Test the message-archive plugin to confirm it can now access the native message ID.

Extra Tips

• To avoid manual patching on every OpenClaw update, consider submitting a pull request to the OpenClaw repository with the proposed fix.
• If you're using a version control system, make sure to commit the changes and update the affected files accordingly.