openclaw - 💡(How to fix) Fix feat: Support for structured `bodyExtras` in message tool [2 comments, 2 participants]

TL;DR

Adding an optional bodyExtras field to the message tool's parameters can provide a structured way to pass metadata alongside human-readable message content.

Guidance

• Review the message tool's current implementation to determine the best way to integrate the proposed bodyExtras field.
• Consider the potential impact on existing integrations and workflows that rely on the current message format.
• Evaluate the benefits of using a structured format like JSON for the bodyExtras field to ensure easy parsing and serialization.
• Discuss the proposal with stakeholders from project #082 and other relevant teams to ensure the new field meets their requirements.

Example

// Proposed message tool parameters with bodyExtras field
const messageParams = {
  message: 'Hello, world!',
  bodyExtras: {
    metadata1: 'value1',
    metadata2: 'value2'
  }
};

Notes

The proposal's success depends on careful consideration of backward compatibility and the needs of various stakeholders.

Recommendation

Apply workaround: Implement the proposed bodyExtras field as described, allowing for structured metadata transmission alongside human-readable messages, to improve the robustness of agent-to-agent communication.