🤖 fix: VS Code webview retry barrier omits the auto-retry stop reason
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 72/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript, vscode
- Domain
- frontend
Research direction
Start by comparing the existing desktop RetryBarrier with the VS Code webview barrier and tracing the existing read-only auto-retry status used by the webview. Make the webview display the matching auto-retry stop-reason line without restoring toggling or Stop controls, then verify the result against the same transcript with a 740px side-by-side comparison.
Written by the indexing model from the issue text.
Description
Follow-up from #4968 (final side-by-side on main 7a235ad68d).
After a non-retryable stream error, the desktop RetryBarrier shows "Stream interrupted", the Retry button, and a second line "Auto-retry stopped: " (e.g. authentication). The VS Code webview shows the barrier and Retry but not the stop-reason line, because #5108 (reduced scope, user-chosen option C) keeps only read-only scheduled/countdown status in the webview.
Acceptance: the webview retry barrier shows the same "Auto-retry stopped: " line as desktop for the same transcript, derived read-only from the existing auto-retry status (no auto-retry toggling or Stop controls added back). Side-by-side screenshot at 740px.
Refs #4968, #5108.
Generated with xum • Model: anthropic:claude-opus-5-5 • Thinking: high • Cost: $98.62
- Dominant language
- TypeScript
- Stars
- 2k
- Forks
- 139
- Avg merge
- 6h 35m
- Merged PRs (30d)
- 819
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No 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 coder/xum
-
approved
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
🤖 Delegated-turn delivery and peer-limit follow-ups from #5311 and #5327Possibly taken @ThomasK33 claimed this today. Open
Maintainers usually reply within 1 day
-
🤖 Compaction follow-up dispatch: remaining follow-ups from #5313Possibly taken @ThomasK33 claimed this today. Open
Maintainers usually reply within 1 day
-
🤖 Concurrency primitive and fileLock hazards found by the formal models (#5309, #5319 follow-ups)Possibly taken @ThomasK33 claimed this today. Open
Maintainers usually reply within 1 day
-
🤖 History persistence follow-ups from the formal-verification fixes (#5312, #5316, #5318)Possibly taken @ThomasK33 claimed this today. Open
Maintainers usually reply within 1 day
Similar issues
-
area/frontend good first issue kind/cooldown
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
voidzero-dev/oxc-angular-compiler#511 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
langchain-ai/deepagentsjs#898 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
anomalyco/models.dev#8509 · 2 comments ·
Maintainers usually reply within 1 day
-
bug documentation P2 UI/UX
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day