Inside Feature Request: Split Chat And Live Exec Logs

When running long commands, OpenClaw’s current UI traps users in a static chat box - response feels delayed, and progress vanishes. Adding a split layout - chat on one side, live exec logs on the other - would transform how engineers and ops teams monitor real-time command flow. Users could keep typing, receive immediate feedback, and stay informed without switching contexts.

This isn’t about replacing chat - it’s about balancing conversation with execution visibility. Live logs stream stdout and stderr in real time, with clear status updates: duration, exit codes, and even pauses to review output. Background tasks stay responsive, and developers gain transparency that builds trust.

Psychologically, this design respects modern workflow rhythms - no more frozen screens during critical operations. It turns passive waiting into active participation. But here’s the catch: without careful handling, streaming logs can overwhelm users with noise. Clear distinctions between output streams and intuitive controls - stop, copy, view history - are essential for usability.

Controversy lurks in the balance: live logging risks exposing partial or sensitive outputs if not carefully scoped. The elephant in the room? Without clear guardrails, bad actors could infer internal logic from output patterns. Implementing strict access controls and anonymized logging protects data while preserving insight.

Ultimately, a split exec panel isn’t just a UI upgrade - it’s a shift toward human-centered control. When execution becomes visible, not hidden, every command feels purposeful. Does your UI let users stay in the loop - or just watch the screen freeze?