Improve Failed Task Visibility and Recovery
Maintainers usually reply within 1 day
@mts755Dev is already working on this.
Since Oct 15, 2026.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 18/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- frontend
Research direction
The payload names no files or components, so first find the failed-task card UI and the task state it reads. Check open pull requests #2 and #456, which are linked to this issue, to see whether they already cover part of the work before starting. Done means failed cards show the reason, timestamp and retry count, retry is offered only for eligible tasks, and repeated clicks cannot trigger duplicate retries.
Written by the indexing model from the issue text.
Description
Problem / motivation
When an AI agent fails to complete a task, users may need more information to understand the failure and decide what to do next.
Proposed solution
Problem:
When an AI agent fails to complete a task, users may need more information to understand the failure and decide what to do next.
Proposed solution:
Add a failure details section to failed task cards that displays the failure reason, failure timestamp, and retry count. For tasks that can safely be retried, provide a Retry Task action and show clear status updates while the retry is in progress.
Screenshot, mockup or recording
Expected benefits:
Makes task failures easier to understand.
Helps users recover from temporary failures.
Improves transparency and user experience.
Reduces the need to inspect technical logs.
Acceptance criteria:
Failed tasks display a clear failure status.
Available failure details and retry counts are shown.
The retry action is available only for eligible tasks.
The task status updates correctly after retrying.
Repeated clicks do not trigger unintended duplicate retries.
This enhancement would make task recovery more user-friendly while improving the reliability and observability of the application.
Alternatives considered
No response
Area
User Experience
Pre-flight
- I attached a screenshot, mockup or recording above.
- I searched existing issues and discussions, and this isn't a duplicate.
- Dominant language
- TypeScript
- Stars
- 273
- Forks
- 211
- Avg merge
- 14h 24m
- Merged PRs (30d)
- 203
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from agentvivekkumar/dontbemichael
-
Windows: a hidden Claude call cannot start when the CLI path has a spacePossibly taken @theshloksschauhan claimed this 2 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
agentvivekkumar/dontbemichael#426 ·
Maintainers usually reply within 1 day
-
Raise Home and Manager setup text to the 14px floorPossibly taken @glenmiracle18 claimed this 1 day ago. Openbug os:windows
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
agentvivekkumar/dontbemichael#416 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 15/100
agentvivekkumar/dontbemichael#499 ·
Maintainers usually reply within 1 day
-
Enhancement: read scans and photos on Windows with the OCR built into Windows, as the Mac already doesPossibly taken @MickyG03 claimed this today. Openenhancement
Difficulty 3/5 1-2 days Newbie friendliness 28/100
agentvivekkumar/dontbemichael#498 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 22/100
agentvivekkumar/dontbemichael#490 ·
Maintainers usually reply within 1 day
All issues in agentvivekkumar/dontbemichael
Similar issues
-
Endpoint links in the tag operations list are below the 24px target sizePossibly taken @AdzerKI claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
ai-driven-qa bug Minor
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
linagora/twake-tasks#435 ·
Maintainers usually reply within 1 day
-
bug domain: database priority: p1 Stellar Wave
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
StellarState/SS-backend#632 · 1 comment ·
Maintainers usually reply within 1 day
-
A2A audit timestamps end in +00:00Z (invalid ISO 8601)Possibly taken @O1sumitkumar claimed this today. Openbug good first issue help wanted python
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
`cf complete zsh >> .zshrc` fails on vanilla zshMay be free again A pull request for this issue was closed without being merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
cloudflare/cf#340 ·
Maintainers usually reply within 1 day