[FEATURE]:Add retry / re-run capability when operation is aborted #5279

Open
opened 2026-02-16 17:50:48 -05:00 by yindo · 0 comments
Owner

Originally created by @doanbactam on GitHub (Jan 13, 2026).

Originally assigned to: @thdxr on GitHub.

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

Problem

When an operation fails with “The operation was aborted.”, there is no way to retry or re-run the last request. Users must manually submit everything again.

Request

Please add one of the following:

  • A Retry button on aborted operations
  • A Re-run last request action
  • Or preserve the last prompt/context after abort

Why

Abort errors are often not user-caused (network, timeout).
Lack of retry makes long or complex workflows painful.

Screenshot

Image
Originally created by @doanbactam on GitHub (Jan 13, 2026). Originally assigned to: @thdxr on GitHub. ### Feature hasn't been suggested before. - [x] I have verified this feature I'm about to request hasn't been suggested before. ### Describe the enhancement you want to request ### Problem When an operation fails with **“The operation was aborted.”**, there is no way to retry or re-run the last request. Users must manually submit everything again. ### Request Please add one of the following: - A **Retry** button on aborted operations - A **Re-run last request** action - Or preserve the last prompt/context after abort ### Why Abort errors are often not user-caused (network, timeout). Lack of retry makes long or complex workflows painful. ### Screenshot <img width="720" height="846" alt="Image" src="https://github.com/user-attachments/assets/34bccee6-44b7-48d5-a424-ddce0212fd95" />
yindo added the discussion label 2026-02-16 17:50:48 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#5279