Skip to content

fix(chat): show why a vendor session cannot launch - #905

Merged
vastsa merged 2 commits into
mainfrom
fix/chat-blank-model-error
Sep 22, 2026
Merged

vastsa merged 2 commits into
mainfrom
fix/chat-blank-model-error

Conversation

@vastsa

@vastsa vastsa commented Sep 22, 2026

Copy link
Copy Markdown
Owner

Summary

  • A vendor-account launch that fails before any message is stored no longer leaves the chat page blank. An error-only assistant row stays in the transcript instead of being treated as an empty home.
  • When the signed-in account's model list does not include the session model, the chat surface shows MODEL_NOT_CONFIGURED and the model id, with a link to settings.

Test plan

  • node --test test/chat-launch-error.test.mjs test/home-empty-layout.test.mjs
  • tsc -p apps/desktop/tsconfig.json --noEmit

A launch failure before any message is stored left an error-only assistant
row that the empty home treated as no transcript, so the chat page went
blank. Keep that row visible, and name a vendor-account model the account
list did not return.
Copilot AI lite review requested due to automatic review settings September 22, 2026 20:01

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

The thinking-only empty-home guard moved into chat-launch-error.ts.
Point the source contract at that helper and at the ChatSurface call.
@vastsa
vastsa merged commit 2685888 into main Sep 22, 2026
4 checks passed
@vastsa
vastsa deleted the fix/chat-blank-model-error branch September 24, 2026 01:54

This branch was previously deployed

1 inactive deployment
Preview — ad301849 Deployed Sep 22, 2026 by vercel[bot]
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.

2 participants