openclaw - 💡(How to fix) Fix [Bug]: Tool calls rendered as raw text in all UIs (control-ui, telegram, tui) [1 comments, 2 participants]

TL;DR

The issue can likely be resolved by updating the rendering logic to handle tool calls correctly, possibly by modifying the UI rendering code to parse and display tool call results inline.

Guidance

• Verify that the tool call results are being returned correctly by checking the API responses or logs to ensure the data is being sent back as expected.
• Check the UI rendering code for any recent changes that may have introduced this issue, focusing on how tool calls are handled and displayed.
• Test the rendering of tool calls in different UI channels (e.g., control-ui, telegram, tui) to see if the issue is consistent across all platforms.
• Review the documentation for the minimax/MiniMax-M2.7 model and OpenClaw 2026.4.5 to ensure that the tool call syntax and rendering expectations are correctly implemented.

Example

No specific code example can be provided without more details on the rendering logic, but the fix might involve modifying a template or a function responsible for displaying tool call results, ensuring it correctly interprets and formats the output.

Notes

The solution may depend on the specific implementation details of the UI rendering code and how it interacts with the OpenClaw and minimax/MiniMax-M2.7 model. Without access to the codebase or more detailed logs, it's challenging to provide a precise fix.

Recommendation

Apply a workaround by temporarily modifying the UI rendering code to correctly handle and display tool call results until a more permanent solution can be implemented, as the root cause seems related to how tool calls are rendered rather than a version-specific issue that would necessitate an upgrade.