Skip to content

Make sure input state is populated even if you're not using the getChatSessionInputState api#309943

Merged
mjbvz merged 1 commit intomicrosoft:mainfrom
mjbvz:dev/mjbvz/patient-monkey
Apr 14, 2026
Merged

Make sure input state is populated even if you're not using the getChatSessionInputState api#309943
mjbvz merged 1 commit intomicrosoft:mainfrom
mjbvz:dev/mjbvz/patient-monkey

Conversation

@mjbvz
Copy link
Copy Markdown
Collaborator

@mjbvz mjbvz commented Apr 14, 2026

cc @DonJayamanne Not sure if this would explain the behavior you were seeing but it could have caused an issue like it

Copilot AI review requested due to automatic review settings April 14, 2026 19:03
@mjbvz mjbvz self-assigned this Apr 14, 2026
@mjbvz mjbvz enabled auto-merge April 14, 2026 19:03
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Ensures the chat session input state is populated from initial session options even when an extension controller does not implement getChatSessionInputState.

Changes:

  • Precomputes previousInputState from controller option groups and request.initialSessionOptions.
  • Reuses previousInputState when calling getChatSessionInputState (avoid duplicate creation).
  • Falls back to previousInputState (instead of an empty state) when getChatSessionInputState is not implemented.
Show a summary per file
File Description
src/vs/workbench/api/common/extHostChatSessions.ts Uses initial session options to populate the input state even without the getChatSessionInputState API, and avoids recomputing previous state.

Copilot's findings

  • Files reviewed: 1/1 changed files
  • Comments generated: 0

@mjbvz mjbvz merged commit f0d746e into microsoft:main Apr 14, 2026
30 checks passed
@vs-code-engineering vs-code-engineering Bot added this to the 1.117.0 milestone Apr 14, 2026
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.

3 participants