openclaw - 💡(How to fix) Fix [Design Feedback] Exec approval UX breaks Telegram mobile-first experience [3 comments, 4 participants]

TL;DR

Route exec output back through the agent for formatting before sending to the user to address the decoupling of approval and output.

Guidance

• To address Problem 1, consider modifying the approvals.exec.mode configuration to route output through the agent for formatting, ensuring users receive formatted output in Telegram.
• For Problem 2, redesign the approval UI in Control UI to be mobile-friendly, allowing for full scrolling of long commands and easy access to confirm/deny buttons.
• To simplify configuration (Problem 3), consolidate approval behavior settings into a single location, such as openclaw.json, to reduce fragmentation and improve transparency.
• Consider implementing a session-scoped approval mode to enhance user experience, especially on mobile devices.

Example

No specific code example is provided due to the lack of detailed implementation details in the issue description.

Notes

The suggested fixes aim to improve the user experience, especially on mobile devices, and to simplify the configuration of approval behaviors. However, the exact implementation details may vary depending on the specific requirements and constraints of the system.

Recommendation

Apply workaround: Implement a session-scoped approval mode and route exec output through the agent for formatting to improve the mobile user experience and simplify approval configuration. This approach addresses multiple problems outlined in the issue and aligns with the core value of a personal AI agent being reachable and usable from mobile devices.