openclaw - 💡(How to fix) Fix [Feature]: sessions_send messages display sender as the sending agent instead of human user [1 participants]

TL;DR

Adding an optional sender or displayName field to the sessions_send API could help distinguish inter-agent messages from human user messages in the UI.

Guidance

• Consider modifying the sessions_send API to accept an additional parameter that specifies the sender's identity, such as agent_name or agent_avatar.
• Consider updating the OpenClaw chat UI to handle this new parameter and display the correct sender information for inter-agent messages.
• Evaluate the impact of this change on existing workflows and user experiences to ensure it does not introduce new issues.
• Test this modification with different multi-agent setups to verify its effectiveness in resolving the issue.

Example

No specific code example can be provided without more context, but the idea would be to modify the sessions_send API call to include the agent's identity, e.g., sessions_send(message, agent_name="Agent B").

Notes

The proposed solution assumes that adding a new field to the sessions_send API is feasible and does not introduce significant complexity or compatibility issues. Further testing and evaluation are necessary to ensure this solution works as expected.

Recommendation

Apply workaround: Add an optional sender or displayName field to the sessions_send API, as this seems to be the most direct way to address the issue without introducing more significant changes to the system.