OpenHands/agent-canvas

[Bug]: Failed messages remain as the most recent message

Closed

#1,196 opened on Jun 5, 2026

View on GitHub
 (1 comment) (0 reactions) (0 assignees)TypeScript (26 forks)github user discovery
buggood first issue

Repository metrics

Stars
 (43 stars)
PR merge metrics
 (PR metrics pending)

Description

Thank you for reporting a bug! 🐛

Please fill out all required fields. Issues missing critical information (version, installation method, reproduction steps, etc.) will be delayed or closed until complete details are provided.

Clear, detailed reports help us resolve issues faster.

  • I have searched existing issues and this is not a duplicate.

Bug Description

When a message fails to send, the failed message remains in the position of the most recent message. All subsequent messages and responses are sent successfully, but the failed message always remains at the top of the conversation, creating a confusing user experience.

Expected Behavior

  • Failed messages should not persist as the most recent message for the remainder of the conversation with out a way to dismiss the prompt.
  • The conversation should display messages in chronological order without failed messages blocking the view.

Actual Behavior

  • Failed message remains at the most recent position
  • New messages appear above the failed message
  • Conversation flow becomes confusing

Steps to Reproduce

  1. Send a message that fails to deliver
  2. Send subsequent messages
  3. Observe that subsequent messages are sent successfully but the failed message stays at the top

OpenHands Installation Method

  • CLI (uv tool install)
  • CLI (executable binary)
  • CLI (Docker)
  • Local GUI (Docker web interface)
  • OpenHands Cloud (app.all-hands.dev)
  • SDK (Python library)
  • Development workflow
  • Other: Agent Canvas (npm)

OpenHands Version

[Please specify version]

Model Name

MiniMax 2.7

Operating System

  • MacOS
  • Linux
  • WSL on Windows
  • Windows (Docker Desktop)
  • Other

Browser (if using web UI)

Chrome

Logs and Error Messages

Paste error logs here

Screenshots and Additional Context

https://github.com/user-attachments/assets/da841ce1-b203-4f01-94fc-5417e7b68654

Suggested fix options:

  1. Add a "Retry" button to failed messages
  2. Implement auto-retry with exponential backoff
  3. Allow users to dismiss failed messages

Note: Issues with incomplete information may be closed or deprioritized. Maintainers and community members have limited bandwidth and prioritize well-documented bugs that are easier to reproduce and fix. Thank you for your understanding!

Contributor guide

Research direction
Investigate the message list component to understand why failed messages are not removed or reordered. Look at the state management for messages and the logic that determines the most recent message.
Tech stack
typescript
Domain
frontend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitTypeScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75