Skip to content

fix(desktop): show why a reply failed when the conversation reopens - #125

Merged
sanchitrk merged 1 commit into
canaryfrom
fix/desktop-reply-error
Nov 1, 2026
Merged

sanchitrk merged 1 commit into
canaryfrom
fix/desktop-reply-error

Conversation

@sanchitrk

Copy link
Copy Markdown
Contributor

A provider failure (missing key, quota, invalid request) reached the desktop only as a live session.execution.failed event. A conversation opened after the failure showed the reply as "Interrupted" with no reason.

thread.history entries now carry an optional error for a reply that ended with stopReason: "error", read from the stored assistant envelope and worded like the live failure (provider/model: reason). A reply the user stopped keeps no error. The desktop shows it in place of "Interrupted".

Validation:

  • vp check and vp run typecheck pass.
  • packages/codework: desktop, recovery and server history tests pass. Two model.list tests need a generated models.gen.json at the repo root and are unrelated.
  • Electron against the latest packages/codework server: reopening a session whose first reply failed for a missing OpenAI key now shows openai/gpt-5.6-luna: openai API key is missing….

🤖 Generated with Claude Code

A provider failure was only sent live, so a conversation opened afterwards
showed the reply as Interrupted with no reason. thread.history now carries
a failed reply's provider/model and reason, and the desktop shows it in place.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@sanchitrk
sanchitrk merged commit d08693c into canary Nov 1, 2026
2 checks passed
@sanchitrk
sanchitrk deleted the fix/desktop-reply-error branch November 1, 2026 11:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant