Skip to content

[pull] main from microsoft:main#917

Merged
pull[bot] merged 26 commits intocode:mainfrom
microsoft:main
Feb 11, 2026
Merged

[pull] main from microsoft:main#917
pull[bot] merged 26 commits intocode:mainfrom
microsoft:main

Conversation

@pull
Copy link

@pull pull bot commented Feb 11, 2026

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

mjbvz and others added 26 commits February 10, 2026 12:21
* Refactor hook execution

* Fix compilation: add IExtHostHooks import, remove unused IHookResult, inline ChatRequestHooks type

* Move hooks property to chatHooks proposal, sync DTS

* cleanup

* Remove dead hook execution code: proxy, RPC, output channel, progress events

All hook execution now happens in the extension via NodeHookExecutor.
HooksExecutionService is now a pure registry (registerHooks/getHooksForSession).

Removed:
- executeHook, setProxy, onDidHookProgress from service
- IHooksExecutionProxy, IHookProgressEvent, HookAbortError, formatHookErrorMessage
- hooksCommandTypes.ts, hooksTypes.ts (dead type files)
- mainThreadHooks proxy setup
- extHostHooksNode., extHostHooksWorker.
- ExtHostHooksShape. protocol
- IExtHostHooks DI registrations
- ChatHooksProgressContribution
- All associated test files

* Remove HooksExecutionService entirely

The service was only a registry for session hooks, but hooks are already
passed directly on the chat request DTO. The registerHooks/getHooksForSession
pattern was redundant.

* Restore modelName support in chatSubagentContentPart that was accidentally removed during merge

* Revert unrelated tabIndex change on chatSubagentContentPart

* Remove empty hooks ext host infrastructure

Delete IExtHostHooks, NodeExtHostHooks, WorkerExtHostHooks,
MainThreadHooks, ExtHostHooksShape, MainThreadHooksShape -
all were empty stubs after hook execution moved to extension.

* Remove mainThreadHooks import from extensionHost.contribution

* Fix DTS comments: env and timeoutSec are values, not implementation promises
* Tweak tips

* add steering
Allow contributed configurations to define additional "search terms"
For #274403

Should let us support non-local sessions. Keeping around id support for backcompat
* experiment background agent display name

* update session type picker to handle background agent display name changes
Store sessionResource as view state instead of id
For #292934

Testing this with a self contained area first: code lenses. Will keep support for the old setting values too to avoid breaking existing settings
* PROTOTYPE: Add growth agent (microsoft/vscode-copilot-chat#3460)

* support vscode.ChatSessionStatus.NeedsInput in chatSessions ext api

ref #292430

* Add isReadOnly flag to chat sessions contributions

  Read-only session types (e.g., Growth) are passive/informational and
  should not be registered as agents, appear in session target pickers,
  or be delegation targets. Commands are still registered to support
  openSessionWithPrompt.

* Collapse isReadOnly and canDelegate branches in _enableContribution

  Both need agent and command registration; picker filtering handles
  keeping isReadOnly sessions out of the UI separately.

  the alternative (and probably ideal) UI is to 'grey out'/'disable' the
  chat input for isReadOnly sessions.  That way we don't have this
 problem at all of a non-functional chatInput

* fix description

* redundant doc

* update test
Start adopting unified js/ts config for code lenses
Reduce amount of data we're passing over to ext host each time an update happens
Add optimized way to update a single chat session item
Add vertical spacing to rendered markdown list items in chat
Use font-weight 600 for bold text in rendered markdown
… toolbars in chat (#294275)

Improve rendered markdown table styling in chat
This is just more clear and returns search results for "agent"
@pull pull bot locked and limited conversation to collaborators Feb 11, 2026
@pull pull bot added the ⤵️ pull label Feb 11, 2026
@pull pull bot merged commit a97da02 into code:main Feb 11, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

10 participants