* Agent Merge: recover from a checks fragment the host refuses
Agent Merge could hang indefinitely on a pull request whose checks
fragment was refused by GitHub, showing the user nothing at all.
When an organization enforces SAML SSO and the signed-in token is not
authorized for it, the checks GraphQL query is refused with HTTP 200 and
a FORBIDDEN error in the body. `CheckRun.checkSuite` is non-nullable, so
the refusal on the GitHub Actions data behind the workflow-name
subselection null-propagates and fails the whole fragment rather than
that one field. Checks then never load, the gate is permanently
indeterminate, and nothing surfaces:
- checks never loaded reads as pending, so the fragment held the fast
poll cadence and re-requested a permanently refused query roughly once
a minute, forever;
- indeterminate was the only gate outcome with neither an action nor a
budget, so the session stayed resident with nothing to show;
- only `authentication` raised an auth requirement, so an `authorization`
refusal never prompted the user to re-authorize.
Recover the fragment and make the failure legible:
- gate the workflow-name subselection and drop it for a repository whose
host refuses it, keeping the checks themselves. Only the rollup request
is retried, and an expected-check-suites refusal degrades to absent and
incomplete, so neither is mistaken for the other;
- raise an auth requirement for `authorization` too, naming the
organization and calling out SSO when GitHub reports it;
- give indeterminate a budget over continuously observed time, so a
pull request that can never be read stops instead of idling while a
turn or a sleeping host cannot exhaust it;
- name the fragment and its error in the indeterminate reason instead of
one string shared by five fragments;
- back off persistent authorization failures, and stop an errored checks
fragment from holding the fast cadence.
Partial check data is still never accepted, so a refused fragment
continues to fail closed rather than reporting checks it could not read.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Request a credential when the snapshot records a refused fragment
Only the first refresh of a subscription reports a failure by throwing, so
raising the auth requirement from the evaluation catch missed the case it
was meant to cover: every later refusal is recorded on the snapshot and
read as an ordinary indeterminate gate, leaving the session waiting on a
credential the user was never asked for.
Detect a refused gate fragment on the snapshot and request a credential
there, once per distinct failure so a persistent refusal does not nag and
a failure after recovery can prompt again. Share one path with the throw
site, and keep the fragment list with the gate that defines it.
Also shorten the comments added with this change to the limits in the
coding guidelines.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Fix launch.ps1 to discover Node.js from fnm
Add fnm directory fallback to Get-UsableNode so PowerShell launcher can find
Node.js installed via fnm when it's not on PATH. Tries PATH first (original
behavior), then checks AppData\Local\fnm_multishells for fnm-managed versions.
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
* launch skill: copy the shared-data-dir so Windows stays signed in
On Windows the GitHub session is stored at StorageScope.APPLICATION_SHARED
rather than APPLICATION - see useSharedStorage and CROSS_APP_SHARED_SECRET_KEYS
in src/vs/platform/secrets/common/secrets.ts. That puts the encrypted session
blob in <shared-data-dir>/sharedStorage/state.vscdb while the DPAPI-wrapped key
stays in <user-data-dir>/Local State.
The launcher copied the profile but handed Code OSS a brand-new empty
--shared-data-dir, so every Windows launch silently started signed out. Signing
in again did not help, because the new session was written to a shared dir that
the next launch discarded. macOS and Linux are unaffected: isWindows is false
there, so the same token lands inside the copied profile.
Seed the run's shared-data-dir from ~/<product.sharedDataFolderName>
(overridable with CODE_OSS_DEV_AUTHED_SHARED_DATA_DIR), and teach the auth
preflight to probe the shared database as well as globalStorage so its warning
is accurate. Also correct SKILL.md, which documented the macOS-only model and
recommended a remedy that cannot fix this on Windows.
Verified end to end: the launched Agents window authenticates against the real
service and completes a chat request without prompting for sign-in.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
* launch skill: address review feedback on shared-data seeding
- Mirror the VSCODE_PORTABLE branch of IEnvironmentService.appSharedDataHome
when resolving the source shared-data-dir, so a session created in portable
mode is found instead of silently falling through to the product folder.
- Stop claiming a missing shared-data-dir means the launch will prompt for
sign-in. ApplicationSharedStorageMain registers application storage as a read
fallback, so profiles predating the APPLICATION_SHARED migration authenticate
from globalStorage with no shared dir at all. Report the missing directory as
a fact and let the combined preflight decide.
- Rewrite the SKILL.md callout that read as contradicting the remedy printed
directly beneath it.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Haiku 4.5 <noreply@anthropic.com>
Narrow internal service dependencies, move runtime collaborators out of AgentService, and replace two-phase initialization with a constructor-complete composition. (Written by Copilot)
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* agentHost: adopt AHP 1.0.0 breaking changes
Syncs the generated protocol types to AHP 1.0.0 and adopts the breaking changes in the agent
host, the workbench chat session handler, and the Agents window provider.
- Removes session-level forking. `CreateSessionParams.fork` and `SessionForkSource` no longer
exist, so the fork configuration, its service plumbing, and the protocol forwarding are
deleted. The editor-window Fork Conversation gesture now forks into a peer chat of the same
session, which is how the Agents window already behaved. Chat-level forking does not change.
- Moves `ChatInputRequestPurpose` into the request `_meta` bag. The protocol no longer models
the purpose, so a new helper writes and reads it. This keeps the ask-user telemetry and the
elicitation classification.
- Replaces the terminal `exitCode` field with an explicit running/exited lifecycle. An exit
without an exit code is now correctly an exit.
- Supplies the owning chat URI on each `TerminalSessionClaim`. The Copilot session runtime
gives the chat URI to the shell tools, the non-pty output streams, and the local bang
command, and the workbench records the owning chat for each observed terminal.
- Renames `SessionLifecycle.CreationFailed` to `SessionLifecycle.Failed`.
- Replaces the annotation `turnId` with an `origin` that holds the session, the chat, and the
turn. Also corrects the persistence check, which discarded restored annotations.
- Adds `MethodNotFound` handlers for the new automation commands. This host does not advertise
the automation capability.
- Corrects the test data that omitted the turn duration. The chat reducer now calculates
`modifiedAt` from that duration instead of the local clock.
(Commit message generated by Copilot)
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* sessions: correct the artifact location helper name
The image carousel entries called rtifactLocation, but the helper is named
sessionArtifactLocation. This broke the build on main.
(Commit message generated by Copilot)
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* agentHost: address review feedback on the AHP 1.0.0 adoption
- Carries an explicit `hasExited` signal through `IChatTerminalOutputSource`. A command can now
exit without an exit code, so chat must not read completion from the optional code.
- Rejects `session/workingDirectoryReplaced`. The action is client-dispatchable, but no provider
advertises `primaryReplacement` and the host applies no backend side effect.
- Migrates annotations that were persisted before the origin change. Their records hold a
top-level `turnId`, which the new check discarded as invalid.
- Derives the owning session for a shell terminal claim from the chat URI. The shell manager is
constructed with a chat URI for a peer chat, so its own scope URI is not the session.
- Sends real timestamps from the end-to-end turn helpers. The chat reducer now calculates
`modifiedAt` from the turn, so a fixed past `startedAt` made a peer chat look stale and removed
its edits from the session changeset.
(Commit message generated by Copilot)
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* agentHost: correct turn data in the protocol integration tests
The chat reducer now calculates `modifiedAt` from the turn action instead of the local clock, so
turn data that was previously ignored must be correct.
- Sends a real `startedAt` from the shared turn helper. A fixed past timestamp made a completed
turn look older than the session that contains it.
- Supplies the required `duration` when the cancellation test cancels a turn. Without it the
reducer calculates an invalid date, throws, and the cancellation never applies.
(Commit message generated by Copilot)
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* agentHost: repair the merge of the AHP 1.0.0 adoption
The merge of main dropped a test helper call and did not apply the terminal lifecycle change to
the tests that main added, which broke the compile and one unit test.
- Restores `createTestAgentService` in the peer chat title test. The merge replaced it with a
direct constructor call, whose arguments no longer match.
- Sets the terminal lifecycle on the two reconnect tests that main added.
(Commit message generated by Copilot)
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* sessions: stop picking the harness by which one has models
The New Session composer replaced the user's harness with the first one
usable without GitHub, which in practice meant the first one that had
published models. Models arrive asynchronously, so a user who picked
Copilot or Codex while Claude was the only harness with a catalog watched
the pick snap back to Claude a moment later.
Drop that substitution. The stored preference wins, and the first harness
in the list is the default when there is no preference.
The draft is also recreated on every session-type change while an explicit
pick is set, even when the pick and the draft already agree. That was
invisible before because the recreate landed on a different harness, and
it is the churn that carried the snap-back. Give the pick branch the same
match check the no-pick branch already has.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
* sessions: clear the upgrade watcher once the pick matches the draft
Address PR feedback:
- Once a servable pick already matches the draft, the watcher can no
longer do anything, so clear it instead of leaving the listener
registered holding the created session. This restores the lifetime
the old fall-through to _createNewSession gave it.
- Condense the inline explanation to one line.
- Cover _createSessionNow's openNewSession arguments so a signed-out
user's explicit pick cannot be substituted again unnoticed.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
* Add trace logging to the multi diff editor
Adds a `MultiDiffEditorLogger` that traces the state transitions which are
hard to reconstruct after the fact when investigating multi diff editor bugs
such as the view jumping while scrolling or files being expanded even though
they were collapsed:
- view model/loading changes, collapsed state changes (no matter who caused
them) and content height changes (annotated when they happen above the
current scroll offset, which is what makes the view jump)
- programmatic scrolling (reveal, restored scroll state, scroll adjustments
coming from an embedded diff editor)
- view state save/restore, including the active diff item, and editor
set/clear input in both the multi diff editor and the sessions Changes
editor
- navigation (go to next/previous change) and editor template acquire/release
The observers are only created while the log level is set to trace and are
disposed again when it is lowered, so nothing is observed in the default case.
Enable with `Developer: Set Log Level...` > `Window` > `Trace`.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Address multi diff editor logging review feedback
- Log the decoded session resource instead of the synthetic
changes-multi-diff-source: URI when the Changes editor input is set.
- Fall back to the authority or scheme in ormatUri, so pathless URIs
no longer produce a blank label.
- Format diff item keys before logging them, so full URIs never leak into
the trace when a persisted active item is missing.
- Guard the doc state aggregation in getViewState/setViewState with
isEnabled, so large inputs pay no logging-only cost when tracing is off.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* agentHost: make MCP SDK registration explicit
Separate Copilot MCP discovery routing from working-directory resolution so client-synced servers declare whether the SDK should discover them from a plugin or receive them in session config. Validate the client metadata that drives the decision and cover malformed and workspace-default cases.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* agentHost: make MCP SDK registration explicit
Make the Copilot MCP registration path observable at the SDK handoff.
- Record whether each MCP server uses plugin discovery or session config.
- Log the final configured and disabled server names at trace level.
- Avoid logging server URLs, headers, commands, environment values, or paths.
(Commit message generated by Copilot)
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* agentHost: use the test service factory
Update the restored-chat test to construct AgentService through the shared test factory.
- Supplies the new service dependency through the existing test harness.
- Restores the client typecheck and Compile & Hygiene CI job.
(Commit message generated by Copilot)
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* agentHost: test MCP projection trace privacy
Cover the trace-level MCP launch projection contract.
- Assert normal and ephemeral registration and disabled-server summaries.
- Verify that URLs, headers, commands, environment values, and paths stay out of the trace.
(Commit message generated by Copilot)
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* agentHost: remove telemetry configuration service
Use the launch-resolved telemetry level when constructing Agent Host telemetry and preserve runtime consent updates through root config. (Written by Copilot)
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* telemetry: preserve strict DI constructor typing
Keep the configuration-service constructor overload visible to strict instantiation while retaining the fixed-level Agent Host factory. (Written by Copilot)
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* agentHost: preserve internal telemetry launch state
Forward the parent-resolved internal telemetry status so removing the settings-backed configuration service preserves telemetry.internalTesting. (Written by Copilot)
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* agentHost: drop internal testing forwarding
Keep Agent Host internal classification based on the product domain check instead of adding a launch contract for the undocumented telemetry.internalTesting override. (Written by Copilot)
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* agentHost: use test service factory
Update the newly merged AgentService test to use the shared factory after the constructor refactor. (Written by Copilot)
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* agentHost: fix Copilot chat fork leaking an in-flight turn
Fixes a race in Copilot chat forking. `_forkSdkChat` computed the SDK
fork boundary from a locally-mirrored SQLite column that is only filled
in after the next turn's `user.message` event streams back from the
SDK. If a user forked a turn while the following turn was still
in-flight, that column read as empty. The code treated an empty read
as "there is no next turn" and omitted the fork boundary entirely,
which silently copied the whole session, including the in-flight
turn's skill invocation and partial work, into the fork.
- Adds `CopilotAgentSession.waitForTurnEventId`, backed by a
`DeferredPromise` on each `CopilotTurn`, so a fork can wait for the
in-flight turn's event ID instead of skipping the boundary.
- Makes `CopilotTurn` a `Disposable` and `_currentTurn` a
`MutableDisposable<CopilotTurn>`, so the turn's SDK event ID promise
is rejected automatically whenever the turn ends, is superseded, or
the session is disposed. This guarantees `waitForTurnEventId` always
settles, so it needs no timeout.
- Updates `_forkSdkChat` to detect an active next turn via
`currentTurnId` and wait for its event ID before forking, failing
the fork outright if that turn never produces one.
(Commit message generated by Copilot)
* agentHost: snapshot active fork boundary before database read
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Rename RemoteAgentHostProtocolClient to AgentHostProtocolClient because the implementation is shared by local and remote agent host services.\n\n(Written by Copilot)\n\nCo-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Default to an installed build, and report missing video tooling
Three problems surfaced running the skill from a fresh checkout.
Nothing ran without a target. With no flags the runner used the build from the
checkout, which only exists after compiling the product, so the documented
starting point failed to launch. Reproducing a reported issue means running the
shipped product anyway, so with no target flag it now finds an installed VS Code
Insiders (falling back to Stable) and logs which one it chose. `--dev` selects the
checkout build, and `--build` still pins an exact install.
A missing ffmpeg was only discovered after the run, as a raw ENOENT, and it threw
out of `runScenario` after the report had been written. The runner now checks for
ffmpeg and ffprobe before launching anything and prints the install command for
the platform, and caption rendering can no longer fail a run that has already
produced its evidence.
The window did not fill the recording. The canvas is 1920x1080 while VS Code
sizes its own window (1440x900 with a workspace, 1200x800 empty), so the capture
showed the window in the top-left corner surrounded by dead space. The window is
now sized to the canvas once recording is on; a window larger than the display
still renders at that size, so this holds on smaller screens.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: adb443eb-11e5-40a1-8608-7f593fa79485
* Find an installed ffmpeg, pace the steps, and classify blocked steps
Follow-up to the same skill run.
Captions were missing even though ffmpeg was installed. A PATH edit only reaches
processes started afterwards, so an editor that was already running never sees
it, and the runner concluded ffmpeg was absent. It now looks in the usual install
locations as well as PATH, which is the difference between an annotated recording
and a raw one on a machine that already has ffmpeg.
Steps flowed past too quickly to read. A caption is only legible for as long as
its step is on screen, and steps that assert rather than type can complete in a
few hundred milliseconds. Each finished step is now held briefly, controlled by
`stepPauseMs` and disabled with `0` for timing-sensitive scenarios.
Steps that cannot be automated were indistinguishable from ones that were merely
unavailable. `skip` now takes `needs: human` or `needs: infrastructure`: the first
means a person has to check it, the second means the harness could do it but
cannot yet, which is an enhancement request rather than a permanent limit. The
distinction is recorded in the manifest, highlighted in the report, shown on the
video caption, and printed at the end of the run.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: adb443eb-11e5-40a1-8608-7f593fa79485
* Report the quality of the build that ran, and finish the target options
Review follow-ups.
The evidence labelled every installed run `Dev`. Quality was read from the
environment, which only describes a build made from this checkout, so a run
against installed Insiders was reported as Dev in both the manifest and the
report - the evidence named the wrong product. An installed build stamps its own
quality in `product.json`, so that is now the source when a build path is given.
This also corrects `--build`, which had the same problem before this change.
Linux missed Snap installs. Snap keeps the app under a read-only revision root,
so a machine with VS Code installed only through Snap found nothing and fell back
to the unbuilt checkout - the exact failure the new default exists to avoid.
The web launcher recorded 1920x1080 while sizing the page to 1440x900, so the
no-empty-margins claim did not hold there. It now matches the canvas while
recording and keeps its established size otherwise, so smoke runs are unchanged.
`--dev` was accepted but undocumented in the runner's own help, which now lists
all three targets.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: adb443eb-11e5-40a1-8608-7f593fa79485
* Detect a staged update instead of timing out
VS Code on Windows applies a downloaded update by swapping the executable during
startup, so a launch attempt exits before showing a window. Playwright then waits
the full launch timeout and reports that the process "likely crashed or hung",
which sends the reader looking for crash dumps that do not exist.
Insiders downloads an update most days, so anyone reproducing an issue will meet
this. A `new_<exe>` beside the target is the marker, and checking for it turns a
60s misleading timeout into an immediate statement of the cause and the fix.
Confirmed the launch failure is environmental rather than harness behaviour: a
bare Playwright launch of the same installed build, with none of this code in the
path, also never receives a window while the update is staged.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: adb443eb-11e5-40a1-8608-7f593fa79485
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: adb443eb-11e5-40a1-8608-7f593fa79485
* Dispose AgentHostPty on terminal exit
* Dispose AgentHostPty with its terminal instance
* Align AgentHostPty disposal with terminal precedent
* Let reconnect supersede a pending AgentHostPty startup
* Agent Host changes for lramos15/agents/vscode-issue-331852-proposal
* Refactor chat input and attachment components for improved performance
- Remove unused code from agentHostInputCompletions and newChatContextAttachments.
- Optimize chatInputPart and chatAttachmentWidgets for better efficiency.
- Update tests for newChatInputPaste to reflect changes in functionality.
* Fix undefined artifactLocation in session artifact images
The image section called `artifactLocation`, but the helper is named
`sessionArtifactLocation`, as the five other call sites use. This broke
compilation and threw `ReferenceError` from the two Session Artifacts
tests that build an image section.
Introduced by #331946 and present on main.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: b8277a07-8be3-4c23-a886-ba92a9c4cac0
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: b8277a07-8be3-4c23-a886-ba92a9c4cac0
* chat: extract a shared large-card primitive for inline cards
Chat has two card tiers. `.chat-confirmation-widget2` is the medium tier and
already had a name; the large tier -- rounded border, panel background, clipped
content, plus a 22px chrome free icon button -- was open coded in four places.
`chatPlanReview.css` made this plainest by taking the medium tier primitive and
overriding it back up to the large one with the same six declarations the
survey and the question carousel open coded.
Name that tier. `chatCard.ts` owns the stylesheet so its position in the bundle
is deterministic rather than decided by module graph order, and exports the
class names plus a `createChatCardIconButton` helper.
The nine icon button copies all carried `!important`, because `Button` writes
its colors as inline styles that no selector can outrank. Rather than move the
`!important` into the shared file, build these buttons with no color options at
all: `Button` then writes empty strings and the stylesheet owns the appearance.
Removes 228 lines of duplicated CSS for 103 shared ones. The one rendering
change is in the question carousel title, which asked for
`--vscode-agents-fontWeight-semiBold`; that token is registered by
`workbench.common.main.ts` but not by the component fixture harness, so the
title fell back to 400 there instead of the intended 600. The generic token is
also the correct one for `workbench/contrib` per the design token guidance.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 14187097-e970-4d2b-8d7c-cfa8c5aa6306
* chat: fix silent arrow key navigation in the question carousel
The single select list mixed two ARIA focus models. It declared
`aria-activedescendant` on the listbox, but auto focus moved real DOM focus to
an option, and arrow keys only updated `aria-activedescendant` without moving
focus. `aria-activedescendant` is only honoured on the element that actually
has DOM focus, so arrowing through options announced nothing to a screen
reader. Focus the listbox instead, which is the element that declares it.
Multi select is left alone: it uses real focus on the item and never sets
`aria-activedescendant`, so its model is already coherent.
Focusing the list also revealed that the rule meant to indicate a focused list
never applied. It was nested inside `.chat-question-list` while also naming
that class, so it compiled to a list inside a list. With `outline: none` set on
both the list and its items, that left keyboard users with no focus indicator
at all on this list. Anchor it with `&` so the selected row picks up active
selection colors while the list has focus, matching the survey and the rest of
the workbench.
Adds characterization tests for the list's keyboard contract -- arrow clamping,
digit selection, digit past the last option moving to freeform, and where focus
and `aria-activedescendant` actually land.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 14187097-e970-4d2b-8d7c-cfa8c5aa6306
* chat: share the listbox ARIA scaffolding between the card lists
The question carousel and the model feedback survey each hand roll a listbox,
and each has to keep three things in agreement: the class that paints the
active row, `aria-selected` on every option, and `aria-activedescendant` on the
container. Keeping that in step by hand is what produced the carousel bug fixed
in the previous commit, and it is silent when it breaks.
`ChatCardListbox` owns exactly that: option registration, the three way state
sync, and focus. Focus is only handed out through `focus()`, which puts it on
the container, so the invariant that makes `aria-activedescendant` work is
enforceable rather than conventional.
Keyboard handling and row rendering stay at the call sites. The survey wraps at
the ends and supports Home/End; the carousel clamps and binds digits; arrowing
commits in the carousel but not in the survey. Those are product differences,
not duplication, and folding them into option flags would have produced two
widgets wearing one name -- so the shared piece is deliberately narrow and
`clampedIndex` / `wrappedIndex` are offered rather than imposed.
This trades a small net line increase for a single place where the announcement
contract can be got right. The option element id format changes as a result; it
is internal and only referenced by `aria-activedescendant`.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 14187097-e970-4d2b-8d7c-cfa8c5aa6306
* chat: adopt the shared card on the tool confirmation carousel
This was the one large card left open coding its own chrome. It kept a
`transparent` border fallback while the other three fall back to
`chat-requestBorder`, which is why it was held back from the earlier
extraction.
That difference is drift rather than intent. The fallback dates from the
original design, where the carousel was fused to the chat input: no bottom
border and a top only radius. It later gained a full border and a full radius
but kept the fallback. More decisively, `input.border` is null only in dark and
light and resolves to `contrastBorder` in both high contrast themes, so all four
cards already agree in high contrast and diverge only in dark and light. A
deliberate borderless treatment would hold across themes.
So converge instead of adding a modifier: the carousel now shows the same
hairline as its siblings in dark and light, and is unchanged in high contrast.
Also drops the duplicated agents/editor background override and the header
actions block, which matched the shared one on all four declarations.
The overlay header keeps its own padding and centre alignment. It is a compact
bar for a collapsed carousel rather than a titled card header, so folding it
into the shared header would be a real visual change for no structural gain.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 14187097-e970-4d2b-8d7c-cfa8c5aa6306
* chat: make the large card tier win where it composes with the medium tier
Plan review carries both tier classes on one element. Its old rule set the
large shell at four classes of specificity, which beat
`.chat-confirmation-widget2`; the shared `.chat-card-large` only ties it, so the
medium tier was winning on stylesheet order and the card had regressed to a 6px
radius and the request border. Name both classes together so the outcome does
not depend on load order.
Also puts the header separator on `var(--vscode-strokeThickness)` to match the
shell border, and condenses the listbox and focus comments to the constraint
that is not obvious from the code.
The carousel test helper now defines `keyCode` on the event rather than passing
it through the init dict. Chromium does accept it there -- the navigation
assertions were exercising the intended branches -- but it is non-standard and
needed a cast, so this matches the survey test helper instead.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 14187097-e970-4d2b-8d7c-cfa8c5aa6306
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 14187097-e970-4d2b-8d7c-cfa8c5aa6306
The pill visibility context menu disabled the toggle entries for kinds the
session reports no data for. They already sit in their own group below the
kinds with data, so keep the grouping but let them be toggled.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
The dropdown affordance used `chevron-down`, whose ink is drawn above the
middle of the pill's 12px glyph slot, and leaned on a `translateY(1px)` nudge
to reach the label's optical centre. Use `chevron-down-compact` instead -- the
glyph the workspace, session type and automation dropdown triggers already use
-- which is drawn on the box centre and so lands on the label without a
transform.
Drop the substring class matchers on the two glyph rules, which defeat Blink's
per-class invalidation, and share the artifact location helper with the pill
debug overlay rather than rebuilding the same hover, aria and tooltip values.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Clear stale isActive on tabs that are no longer active
`_onDidTabActiveChange` marked the newly active tab's cached DTO as active
but never cleared the flag on the tab that was active before. Since the
label, dirty, pin and preview handlers patch a single field and re-send the
whole cached DTO, updating a *background* tab shipped a stale `isActive:
true` to the ext host, which then repointed the group's active tab at a tab
the user never switched to.
The effect was that changing a background webview panel's `iconPath` or
`title` (or its dirty/pin/preview state) silently flipped
`tabGroups.activeTabGroup.activeTab` to that background tab, with no change
to what the workbench actually renders or focuses.
Fixes#331914
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Keep the two cached tab DTO copies in sync
The MultiDiff resources listener replaced `tabInfo.tab` with a freshly built
DTO, but the group's `tabs` array still referenced the original object. Once
those two caches diverged, clearing `isActive` while iterating the group array
left the replacement DTO in `_tabInfoLookup` untouched, so a later label,
dirty, pin or preview update on a background multi diff tab could still ship a
stale `isActive: true` to the ext host.
Refresh the DTO in place instead so both caches keep pointing at the same
object and cannot drift apart.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Render the session changes pill from a cache
A session reports its changes late, so its changes pill only appeared some
time after the session was opened. Remember the pill last shown for a
session in a bounded, globally stored cache (30 entries, oldest evicted
first) and render it optimistically until the session reports its own
changes.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Potential fix for pull request finding
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
* Potential fix for pull request finding
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
* chat: verify workspace trust for a session's folders before sending
Sending a message to an agent-host chat now verifies workspace trust for
every local folder the session will run in — an existing session's persisted
working directories, or a new session's requested ones — prompting per
untrusted folder and aborting the send if any is declined. Viewing the chat
and the agent list still requires no trust.
Resuming a session whose folder is no longer trusted therefore re-prompts
instead of running untrusted, and the gate reads the session's authoritative
persisted folders (not the current workspace) so an unopened session cannot be
resumed against an untrusted folder just because the open workspace happens to
be trusted.
* chat: check session folder trust in parallel with a fast path
Resolve each folder's trust up front via getUriTrustInfo in parallel and
return immediately when every folder is already trusted (the common case),
instead of issuing a sequential trust request per folder. Only genuinely
untrusted folders are prompted for, still one at a time since the trust
dialog is modal.
* Agents - limit creating a session from a pull request in the same repository, but ensure that the worktree is set up correctly
* Remove tests related to code paths that were removed
* First cut of TS7 context
* WIP
* Bind events correctly
* First TS7 implementation.
* First cut of TS7 context providers
* Minor improvements
* Bug fixes for TS7 context provider
* Add setting to enable TS7 language context
* Use getSymbolsInScope
* Implement nes rename on TS7 Api
* First cut of code review
* Add the TS7 enablement settings
* Some bug fixes
* Some final fixes
* Make the shared API work
* Reject nes rename on symbols from libs
* Consider typescriptteam.vscode-typescript extension id
* Move tests to test folders
* Fix registration code.
* Handle cancellation correctly
* Fix test case and awaits
* Make inflight request fail save
* Implement correct dispose
* Fix failing test
* Potential fix for pull request finding
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
* Use 7.0.2 again
---------
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
* Agent Host changes for sbatten/agents/remove-unnecessary-copilot-token-usage
* Remove unnecessary Copilot token usage in agent host service and tests
sessions: remove session metadata setting
Make the new session tabs and input metadata presentation unconditional, and remove the retired header/tab fallback paths and fixtures.\n\nCo-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Adds `isExternal` to every session-scoped telemetry event, adds
`pullRequestCount` / `pullRequestStatus` to the session summary event,
and stops the `agents/requestSent` session counts from counting the
session the request was sent to.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Batch and reuse DOM measurements across hot UI paths, replace per-mousemove geometry reads with element boundary events, and move terminal gutter alignment into CSS.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Opening a session spans the sessions list, the chat model load, an AHP
round trip and the agent host's database reads before anything renders,
but the timeline had large unlogged gaps. Add trace markers along that
whole path - for both the Agents window list and the workbench chat
sessions list - carrying the session resource so a single open can be
followed through the log.
Markers were only added where none existed; the already-instrumented
ChatWidgetService.openSession and ChatViewPane.loadSession are left
alone.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Agent Host changes for osortega/agents/review-chatfindmodel-widget-editor
* chat: index only the text a response renders in Find
Find counted matches that had no DOM node to land on, so the result count
overstated the total and navigation walked past positions it could never
reach. Three separate causes, each fixed where the text is indexed rather
than compensated for during navigation:
- Markdown link targets were indexed. `renderAsPlaintext` emitted a list
item's raw source instead of parsing its tokens, so a link kept its
target: a response listing its edits as `[src/](/some/path)` indexed the
path, of which only the label renders. Adds an opt-in
`parseListItemTokens` so the 90+ existing callers are unaffected.
- Filtered responses were indexed. The renderer drops the references slot,
the body and the citations for a filtered response, keeping only the
error message, which also shifted every predicted part index for the row.
- Parts merged into one block were fused. Plaintext is trimmed per part and
then concatenated, so `See ` + `foo.ts` + ` for details` was indexed as
`Seefoo.tsfor details`, hiding text that is plainly on screen.
Removes `dropActiveMatch`, which existed to correct the count after the
fact and made the total change as the user navigated.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* chat: name the plaintext option for what it guarantees
`parseListItemTokens` described marked's data model rather than the
output, and named only the case that surfaced the bug: the option also
reduces bold, emphasis and code spans, and swaps the block-level text
renderer. `omitMarkdownSyntax` states what the caller gets, so a future
leak fixed in another renderer folds in without a second option.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* chat: address Find review feedback
- Only schedule a debounced search when the query or options differ from
what the model last searched. An option toggle reaches `_onInputChanged`
after the base state listener has already run `findFirst`, so the second,
identical search left Enter flushing it instead of advancing a match.
- Keep a segment's *last* `limit` matches. The per-segment cap was applied
before the array was reversed, so a single over-limit segment retained its
oldest occurrences and dropped the newest ones navigation reaches first.
- Yield once before the result count snapshots state. `FindInput.onDidChange`
fires before the `onInput` handler that schedules the search, so the waiter
saw nothing pending and reported the previous query's matches.
- Condense multi-line method-body comments to one line.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* chat: separate a nested list from the item holding it
Verified `renderAsPlaintext` against the vendored marked and found two
things wrong with the list-item change.
Parsing a tight item's tokens with `top = false` skips the paragraph
treatment that gives block content a boundary, so an item holding a nested
list ran straight into it: `- outer\n - inner [link](/t)` produced
`outerinner link`. Parsing as top-level restores the break and also drops a
redundant blank line from loose lists.
The two new assertions expected a single newline between list items where
marked emits two; `renderer.list` joins items that already end in one.
Default output is unchanged in every case, including the pre-existing
plaintext suite.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Ladislau SzomoruandGitHub
Vijay UpadyaandGitHub
Kyle CutlerandGitHub
Vritant BhardwajandGitHub
Anthony KimandGitHub
vritant24
Don JayamanneandGitHub
SteVen BattenandGitHub
Sandeep SomavarapuandGitHub
Bhavya UandGitHub
