Skip to content

fix(vsce): push restored messages to webview after session restore#1338

Merged
lewis617 merged 1 commit into
mainfrom
worktree-shallow-brave-storm
Jul 3, 2026
Merged

fix(vsce): push restored messages to webview after session restore#1338
lewis617 merged 1 commit into
mainfrom
worktree-shallow-brave-storm

Conversation

@lewis617

@lewis617 lewis617 commented Jul 3, 2026

Copy link
Copy Markdown
Collaborator

Problem

When selecting a session in the VS Code extension session selector, the conversation history (messages) was not loaded. The session dropdown would switch to the selected session, but the message list remained empty or showed the previous session's messages.

Root Cause

called which internally triggered the SDK's callback. However, in the VSCE layer, the callback only stored the messages into — it did not call to push the updated message list to the webview.

This is in contrast to , which explicitly calls after .

Fix

Add after in . The flag (already set before the call) ensures the update fires immediately rather than being throttled.

Testing

  • Verified via debug logging that session list data flows correctly (6 sessions fetched and sent to webview)
  • The missing link was specifically the message list not being pushed after restore
  • Type-check and lint pass

ChatSession.restoreSession() called agent.restoreSession() which stored
restored messages via onMessagesChange callback, but never called
throttledUpdateChatMessages() to push them to the webview. This caused
the session selector to switch sessions without loading the conversation
history. Add the missing throttledUpdateChatMessages(this.messages) call
after agent.restoreSession(), mirroring the pattern used in clearChat().
@lewis617 lewis617 merged commit 6ea5549 into main Jul 3, 2026
1 check passed
@lewis617 lewis617 deleted the worktree-shallow-brave-storm branch July 3, 2026 04:32
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