openclaw - 💡(How to fix) Fix [Bug]: NO_REPLY / TUI completely unresponsive after 2026.4.1 update — model fails silently with no error shown [1 participants]

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.

• No error shown in TUI, no log output visible to user 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.

1. TUI returns NO_REPLY with no error feedback (this issue)

TL;DR

Downgrade to a previous version or wait for a patch to address the NO_REPLY issue in TUI, as the current version 2026.4.1 has introduced multiple regressions.

Guidance

• Verify that the issue persists across different models and sessions to rule out model-specific or session-specific problems.
• Check if there are any open issues or discussions related to the NO_REPLY problem in the project's issue tracker or community forums for potential workarounds or fixes.
• Consider reaching out to the development team or maintainers for a rollback guide or a temporary fix, given the significant impact of this issue on productivity.
• Review the release notes and changelog for version 2026.4.1 to understand the changes that might have led to this regression.

Notes

The provided information suggests that the issue is related to the update to version 2026.4.1, but without more technical details, it's challenging to provide a specific code-level fix. The presence of multiple regressions in the same update indicates a need for a more comprehensive solution or rollback.

Recommendation

Apply workaround: Given the significant impact of the NO_REPLY issue and other regressions introduced in version 2026.4.1, downgrading to a previous version or waiting for a patch that addresses these issues seems to be the most prudent approach until a stable fix is available.