Connor Peet

agentHost: fix orphaned client tool calls after window reload - A window reload reconnects with a new clientId but an identical tool list. The cached SDK session was reused with the dead window's clientId baked in, so every later client tool call was stamped with that dead id, routed to passive render, and hung forever with nobody to invoke it. - Introduces a live, shared ActiveClientState so the owning clientId is read at tool-call stamp time instead of being frozen at session creation, and makes the staleness check restart only on structural tool/plugin changes — a clientId-only change no longer needlessly restarts (Copilot) or yield-rebinds (Claude) the session. - Adds a server-side safety net so a client tool call stamped for a client that is not connected (including one that disconnected before the call was even issued) fails after a grace window rather than hanging, with the grace measured from when that client was last seen. - Lets a completion that races ahead of the SDK tool handler resolve via a buffered result, preserving the previous out-of-order tolerance. Fixes #319641 (Commit message generated by Copilot)

agentHost: initial implementation of /btw Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

agentHost: support multiple active clients per session Adopt the agent host protocol update that moves from a single active client per session to multiple active clients, and make the agent implementations model and merge them correctly. Protocol + UI/server: - SessionState.activeClient? -> activeClients[]; session/activeClientChanged is split into session/activeClientSet (upsert by clientId) and session/activeClientRemoved; session/activeClientToolsChanged carries a clientId. - The UI adds itself via session/activeClientSet and never removes itself. - The server removes a client from activeClients (and cancels its in-flight client tool calls) on unsubscribe, and on reconnect when the client does not resubscribe to a session where it was still active. Disconnect keeps the client active during the grace window; the grace timeout removes it and fails its pending tool calls if it never returns. IAgent implementations: - Replace setClientTools/setClientCustomizations with a per-client handle API: getOrCreateActiveClient(session, {clientId, displayName}) -> IActiveClient (mutable readonly-array tools/customizations accessors) and removeActiveClient(session, clientId). - Add shared node infra ActiveClientToolSet (per-session, clientId-keyed tool registry with merge-by-name + ownerOf) and adopt it in Copilot, Claude and Codex so multiple active clients' tools/customizations are stored, merged (deduped, first-inserted client wins) for the SDK, and tool calls are stamped to the owning client. - Guard teardown races: Copilot invalidates an in-flight customization sync on removeClient; Claude removes tools synchronously and serializes customization removal through the session sequencer, and prunes cached handles on session disposal. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

agentHost: adopt new customization protocol shape Brings the platform and workbench code in line with the reorganized AHP customization types: containers (PluginCustomization, DirectoryCustomization) carry the children (agents, skills, prompts, rules, hooks, MCP servers) discovered inside them. - Replaces CustomizationRef/SessionCustomization/CustomizationAgentRef with the new Customization tree, plus ClientPluginCustomization for client-published plugins. Adds a customizationId(uri, range?) helper for minting session-unique ids that disambiguate inline manifest declarations. - Updates IAgent and IAgentPluginManager: getCustomizations/getSessionCustomizations return Customization[]; setClientCustomizations/syncCustomizations take ClientPluginCustomization[]; setCustomizationEnabled now takes the opaque id. - Reworks copilotAgent's PluginController + SessionDiscoveredEntry around the flat Customization shape with the CustomizationLoadStatus enum and a children array; SessionCustomizationUpdated dispatches the whole entry. - Restores the legacy plugin-only agentHostCustomizationConfigSchema so existing agent-host-config.json files keep working; entries are lifted into the new Customization container shape at read time by getAgentHostConfiguredCustomizations / toContainerCustomization. - Renames toCustomizationAgentRefs to toAgentCustomizations; drops the redundant enabled flag on ChildCustomization (children inherit their container's enablement). customAgents.getEffectiveAgents now walks children filtered by CustomizationType.Agent. - Updates the workbench item provider, active-client service, harnesses, custom-agent pickers, and the remote harness to the new types; toStatusString/toStatusMessage drive UI status off CustomizationLoadStatus. - Adapts all consumer tests (reducers, agentPluginManager, agentSideEffects, copilotAgent, mockAgent, syncedCustomizationBundler, resolveCustomizationRefs, localAgentHostSessionsProvider, remoteAgentHostCustomizationHarness, agentHostAgents/AgentPicker) to the new shapes. - Cleans up a stale URI auto-generated import in channels-session/actions.ts. (Commit message generated by Copilot)

wip: connection unification

chat: show side chats as session tabs /btw now branches the active chat context into standard Agents tabs instead of a separate side chat surface. This keeps hidden tool subagents out of the visible tab model while preserving compatibility with the legacy fork-based side chat protocol. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Fix follow-up subagent permission routing Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Agent host: persist chat drafts Store chat drafts in the per-session database and restore draft text, attachments, model, and agent selection into the chat input. Rebuild restored Copilot turns with best-effort model and attachment metadata while avoiding unresolved subagent names as agent URIs. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Add AHP MCP server lifecycle controls Wire AHP-backed MCP server start and stop through agent host sessions, surface session-aware controls in MCP UI, and update MCP editor affordances to reflect active agent-host state. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

AH: MCP server inventory + sampling + ListMcpServer integration * Wire MCP servers and sampling from agent-host sessions over the Agent Host Protocol. CopilotAgentSession advertises the standard MCP app capabilities (sampling + resources) and routes notifications by channel scheme. Seeds the inventory from `rpc.mcp.list` at subscription time so restored sessions and eagerly-configured servers populate without waiting for live events. * Expose MCP servers through a new `getMcpServers` method on `IAgentHostCustomizationService` (workbench layer) and `IAgentHostSessionsProvider` (sessions layer). Returns rich `IAgentHostMcpServer` objects that encapsulate the `SessionCustomizationToggled` dispatch so callers don't depend on the low-level action protocol. * Extend `MCP: List Servers` to default to the agent-host session's servers when an agent-host chat is focused, with a "Show locally configured servers..." back entry to switch to the local picker. Adds a per-server detail picker with an enable/disable toggle, registered as `workbench.mcp.agentHostServerOptions`. * Move the active-client claim from session-open paths to the first turn so that opening a session doesn't dispossess another client that's mid-turn elsewhere. Update affected tests to assert the new "claim on first turn" semantics. * Rework agent plugin caching to use per-nonce subdirectories so multiple revisions of the same plugin can coexist on disk. A long-running session can keep referencing an older nonce while a newer one is materialized; stale nonces are evicted opportunistically once they're no longer locked. Includes tests for the new layout and the locked-directory retry path. * Include MCP-only plugins (no prompt files) in the customization refs so their servers are still synced to the harness. Compute plugin nonces from `fileService.stat` mtime to keep the client-side fingerprint stable across syncs. * Refresh `SessionCustomizationDiscovery` non-recursive watchers to use `e.contains` so they fire on the watched URI itself. Adds tests for: MCP seeding (success + failure), per-nonce plugin materialization and eviction, MCP-only plugin inclusion, and the new active-client claim timing. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

agentHost: support running tasks in remote workspaces Adds a pluggable task-runner registry (ISessionTaskRunnerRegistry) so the agents window can dispatch session tasks through different runtimes: - WorkbenchSessionTaskRunner (priority 0) preserves today's ITaskService path for local file workspaces. - AgentHostSessionTaskRunner (priority 100) opens an agent-host terminal via IAgentHostTerminalService and sendText's the resolved command, so tasks now work in remote agent-host sessions where there's no extension host. Also adds a WorktreeCreatedTaskDispatcher contribution that runs `runOptions.runOn === 'worktreeCreated'` tasks once per session; the cloud-agent provider opts out via a new ISessionCapabilities.runsWorktreeCreatedTasks flag because its server-side host already runs those during provisioning. resolveTaskCommand handles command/args (with POSIX shell quoting honoring strong/weak/escape CommandString metadata), OS overrides, npm scripts, and dependsOn chains (sequence -> '&&', parallel -> backgrounded subshells with trailing wait). Fixes #312052 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

agentHost: adopt AHP protocol updates Syncs the agent-host-protocol types to upstream 740f6cf and adopts the breaking changes from PR 188, while reverting PR 191 (Changeset/ChangesSummary rename) which we are not ready to adopt yet. - Replaces `toolClientId` on tool-call actions with `contributor: { kind, clientId }` so the renderer/server can distinguish client vs MCP-provided tools - Plumbs the new `ChangesetOperationStatus` field through commit-operation provider, tests, and reducer fixtures - Adds the required `enabled`/`state` fields to McpServerCustomization stubs across tests and pluginParsers - Narrows `ISyncedCustomization.customization` and related helpers to `PluginCustomization` so per-plugin `children`/`load` access is type-safe - Reverts PR 191 changes in the synced protocol files: keeps `ChangesetSummary` (with `additions`/`deletions`/`files`) and drops `ChangesSummary` from `SessionSummary` (Commit message generated by Copilot)

mcp: add persistent server enablement scopes Persist profile and workspace enablement for agent-host-only MCP servers while keeping session overrides independent. Apply durable changes immediately before turns and group profile, workspace, and session actions consistently. Fixes #326167 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Soft reconnect for remote agent host protocol client Persist the protocol client across transport drops. On WebSocket close or watchdog timeout, install a fresh transport via an optional constructor-supplied factory and issue a `reconnect` RPC with the existing clientId, last-seen server seq, and active subscription URIs; server replies with a replay buffer or fresh snapshots. Outgoing requests and buffered notifications gate on a DeferredPromise until the handshake completes, then drain (with dedup of optimistic actions the server already echoed). State is modeled as a discriminated union so reconnect-only fields can't leak into other states. Service-layer surfaces Reconnecting as `connecting` so the UI doesn't flicker.

wip: connection unification renderer side

agent host: lenient protocol negotiation + CLI-driven server upgrades Replaces the exact-match version check in `ProtocolServerHandler._handleInitialize` with a semver-caret negotiator (`negotiateProtocolVersion`) that picks the highest offered version compatible with the server. When negotiation still fails and the agent host was spawned by a managing VS Code CLI (signalled by the new `VSCODE_AGENT_HOST_MANAGEMENT_SOCKET` env var), the `UnsupportedProtocolVersion` error advertises a `_meta.vscodeUpgradeMethod = "_vscodeUpgrade"` hint. The client can then invoke that method on the same transport (callable pre-`initialize`) to request a server upgrade. The CLI runs a hyper-based HTTP control server on a unix socket / named pipe. `POST /upgrade` synchronously downloads the latest release, returns a serde-derived response (`{ok, upgradeNeeded, upgradeStarted, runningCommit, latestCommit, restartDelayMs, error}`), and then schedules a kill+respawn after a 3 s drain delay so the response can hop back through the proxy before the transport drops. Single-flight via `upgrade_in_progress: AtomicBool`; the listener is started lazily from `AgentHostManager::start_server`. UI: - `RemoteAgentHostConnectionStatus.incompatible` carries `vscodeUpgradeMethod` (read from `_meta`). - A `watchForIncompatibleNotifications` autorun on each provider raises a one-shot warning notification on transition into `incompatible`, with "Update Server" (when the host advertised it) and "Show Options" primary actions. - `runServerUpgrade` is shared between the notification action and the per-host quickpick. It drives a progress notification with a per-second "Restarting in Ns..." countdown and observes `connectionStatus` so it bails out if some other code path is already reconnecting.

make it work

agentHost: use lock-free endpoint registry Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Agent host: align tests with chat channels Fix client-tool completion routing to resolve providers by parent session while preserving the originating chat channel for provider callbacks. Update agent host unit and protocol fixtures to dispatch chat actions on explicit AHP chat channels and keep subagent chat state separated from parent sessions. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Agent host: require chat URI for sends Make agent sendMessage receive both the parent session URI and the owning chat URI explicitly. This keeps default-chat sends from being mistaken for base64 session IDs and preserves the strict chat-channel invariant. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>