Summary

After updating to 2026.4.1, the TUI returns NO_REPLY for every message with zero feedback to the user. The agent appears idle but never responds. No error, no timeout message, no indication of what failed. The session is completely unusable.

This compounds the exec approval regression also introduced in 2026.4.1 — between the two issues, zero work has been possible for an entire day.

Behavior

• Send any message in TUI → NO_REPLY
• Status shows connected | idle — gateway appears healthy
• No error shown in TUI, no log output visible to user
• Model: minimax/MiniMax-M2.5
• Session: openclaw-tui

Expected behavior

If the model/provider is failing, the TUI should show an error message explaining why — not silently return NO_REPLY as if the message was never sent.

Combined impact of 2026.4.1

This is the third distinct breakage from this single update:

1. Sandbox auto-enabled, blocks all exec (see [Bug]: Sandbox enabled by default on update breaks all exec for existing single-user setups #58885, [Bug]: exec security defaults to allowlist mode after update — no migration path for existing operator setups #59003, [Bug]: Update 2026.4.1 broke exec completely for existing setups — full day of work lost #59006)
2. Exec approval system impossible to disable (see [Bug]: tools.exec.ask=off and exec-approvals.json defaults ignored — approval popups cannot be disabled #58881)
3. TUI returns NO_REPLY with no error feedback (this issue)

A full working day lost. Not one task completed. This update should not have shipped without a migration path and rollback guide.

Environment

• Version: 2026.4.1
• Platform: macOS, LaunchAgent gateway
• Model: minimax/MiniMax-M2.5