Feature Request: Offline Message Handling and Resend/Delete UI

When a user sends a message while offline or when a network request fails, the application does not provide clear feedback or recovery options. Messages remain in a pending state indefinitely, cannot be retried or deleted through the UI, and are lost entirely on page reload.

This results in poor reliability, confusing user experience, and potential data loss.

Current Behavior

1. User sends a message while offline or during a network failure.
2. The message appears in the chat list with a pending or faded style.
3. The network request fails or times out.
4. The message remains in a pending state indefinitely.
5. No error indication is shown.
6. No retry or delete action is available.
7. If the page is reloaded, the pending message disappears completely.

Screenshots

Proposed UI

Problems Identified

• No distinction between pending and failed messages
• No visual error feedback to the user
• No ability to retry or delete failed messages
• Failed and pending messages are stored only in memory
• Messages are lost on page reload

Desired Behavior

When a message fails to send due to offline status or a network error:

• Message status should transition from pending to error

• An error icon (for example, an exclamation mark) should be displayed next to the message

• Clicking the error icon should present the following actions:

  • Resend: Retry sending the message
  • Delete: Remove the message from the local list

Start by tracing the message-sending flow, pending-state handling, and local message storage described in the issue. Verify the failed-message UI can show an error state with resend and delete actions, and that pending or failed messages survive a page reload.