* Prepopulate Find textbox
* Add warning taken from preload.ts
* Small changes
* Refactor preload script comments for clarity and security emphasis
* Small comment change
* Small comment change
* Update comment
* Use isolated world instead of main world
* Comment update
* Update comment
* Update comment
* PR Feedback
* Small comment
* Update status bar item with hovers
* PR feedback, revert test change
* Added setting to control update status bar visibility
* Rename 'onAction' to 'actionable' for update status bar setting
* Bug fixes
* Fix flaky tests
* Initial plan
* Add ChatContextKeys.enabled check to Simple Browser overlay
- Import ChatContextKeys and observableContextKey
- Add IContextKeyService injection to SimpleBrowserOverlayController
- Check ChatContextKeys.enabled in constructor (early exit if disabled)
- Observe chatEnabled state reactively in autorun to hide overlay when AI features are disabled
- Hide overlay when either chat is disabled or no active editor
Co-authored-by: jruales <1588988+jruales@users.noreply.github.com>
* Remove trailing whitespace
Co-authored-by: jruales <1588988+jruales@users.noreply.github.com>
* Fix overlay reappearing when AI features are re-enabled
Remove early exit check for ChatContextKeys.enabled in constructor.
The reactive autorun already handles showing/hiding based on chat
enabled state, so the controller should always initialize to allow
dynamic toggling of AI features without requiring VS Code restart.
Co-authored-by: jruales <1588988+jruales@users.noreply.github.com>
* Make chat.sendElementsToChat.enabled reactive for immediate toggling
- Import observableConfigValue utility
- Remove early exit check for sendElementsToChat.enabled
- Create observable for chat.sendElementsToChat.enabled configuration
- Update autorun to also check isSendElementsEnabled
- Overlay now shows/hides immediately when toggling both chat.disableAIFeatures and chat.sendElementsToChat.enabled
Co-authored-by: jruales <1588988+jruales@users.noreply.github.com>
* Fix default
---------
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: jruales <1588988+jruales@users.noreply.github.com>
Since https://github.com/microsoft/vscode/commit/ebaa450e15ddf03d2350a7264a3e931dce0eeb4b the following sequence can happen:
0. User triggers and then closes UI for a new background session
1. An agent makes edits to files in a background chat session
2. The files are modified in the session, and then kept automatically
3. The untitled chat completes. Because there is now no active UI and
newly no modified files in the session (so the self-refs in ChatModel
constructor/startEditingSession are not being maintained) the session
is disposed.
4. Migration from the untitled->titled session happens. However as the
session is now disposed, when the edit session is transferred, the
text models used to drive the edit session is gone and the migration
fails.
5. This leaves the world in a torn state and causes #292174.
Fix was to address the underlying issue and hold a reference to the
untitled session while the migration happened to avoid transferring
disposed model.
This is needed so that we can switch between the ts6 and ts-go without having to change any settings. Longer term the plan is to make ts-go reuse the same formatter id. We will make that change once we ship tsgo builtin