* agentHost: restore system notifications within turns
Persist system-initiated notification boundaries and map unmarked SDK notifications back to response parts during history reconstruction. Coordinate boundary writes with replay so restored transcripts match live behavior.
(Written by Copilot)
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* agentHost: stream system notifications during active turns
Forward system notification response parts through the live turn observer, while avoiding duplicate progress when reconnecting to an active turn. Remove the unnecessary history/database workaround from the previous commit.
(Written by Copilot)
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* agentHost: simplify notification reconnect tracking
Use the active-turn response-part snapshot boundary instead of notification-specific counters when deciding which notifications still need live emission.
(Written by Copilot)
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* chat: render persistent system notification response parts
Add a native chat response content kind for system notifications so in-turn notifications use the same compact checked-row treatment as system-initiated requests without disappearing when later content arrives.
(Written by Copilot)
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* agentHost: restore Copilot system notifications
Use persisted assistant turn boundaries to restore in-turn notifications as response parts and idle wake-up notifications as system-initiated turns.
(Written by Copilot)
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
- Add a "bang command" feature: in any chat agent, a message starting with
`!` runs as a terminal command (via the existing agent-host terminal/shell
integration) instead of being sent to the model. The host emits a
transcript-only tool-call response for the command.
- Persist host-injected "local turns" (`!command` and `/rename`) so they
survive reload; fork/truncate/rename resolve them to the preceding concrete
SDK turn. Handled uniformly per-chat (default, peer and subagent chats).
- Refactor local command handling into a pluggable `LocalChatCommandRegistry`
with self-contained `AgentHostLocalCommands` dispatcher, extracting the
logic out of `AgentSideEffects`. Add `renameLocalCommand` and
`bangLocalCommand`.
- Extract shared helpers: `shellCommandExecution` (agent-agnostic shell exec
core) and `persistSessionMetadata`.
- Fix peer-chat truncation routing: `truncateSession` now takes the chat URI
and routes peer chats to their own backing session.
- Fix truncate no-op after forking into a second peer chat: `SessionDataService`
keyed every peer chat of a session onto one data dir/DB (chat id lives in the
URI authority, which `AgentSession.id` dropped), so a second fork's
`vacuumInto` failed with "output file already exists" and the forked chat
never inherited its turn event IDs. Key now includes the authority; both fork
copy sites also clear any stale target DB first.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Skip chat view relayouts while the widget is hidden so dynamic-height rows are not measured against detached or display-none DOM.\n\n(Written by Copilot)\n\nCo-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Use the response render cursor, rather than stream word statistics, to detect content that has not yet been displayed. Add regression coverage for initial catch-up behavior.\n\n(Written by Copilot)\n\nCo-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* sessions: add ephemeral running-subagents chip above the chat input
Adds a status chip above the composer that appears only while the
currently-viewed chat has running (or attention-needing) subagents, so a
parallel background fan-out has a glanceable overview the transcript
can't provide once it scrolls.
- Shows "N running" with a spinner; escalates to "N need attention"
(warning color) when any subagent is blocked (SessionStatus.NeedsInput).
- Hidden entirely while idle, so it adds no chrome when nothing is running.
- Clicking opens a menu of the running subagents (attention-needing first,
with the current step surfaced from the chat description); selecting one
reveals its read-only tab.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* sessions: name the single running subagent in the status chip
When exactly one subagent is running, the chip now reads
"Running subagent: <title>" with its live progress inline; for more than
one it stays "N subagents running". The subagent title is read reactively
so it updates when the worker is auto-titled.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* sessions: drop needs-attention state from running-subagents chip
Show only running (InProgress) subagents. Removes the NeedsInput
"needs attention" escalation, its warning styling, and the attention-first
ordering; the chip is purely a running-workers indicator now.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* sessions: make input-part mounting idempotent (CCR feedback)
Key the banner/chip mounting off the desired final order
([subagentsNode, bannersNode, ...]) so `_ensureBannersMounted` is a true
no-op once the DOM has settled, instead of performing two insertBefore
mutations on every doLayout()/resize.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* sessions: update changes view file sections
Rename the external session files section to Other Files and align its rows with the main changes list. Update split sizing so CI and file changes cap to their content while Other Files takes remaining space, including a 140px empty file-changes minimum.
Add full Changes view component fixtures for the main split-view states.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* sessions: preserve changes view sash size
Fire the tree pane SplitView change event without a preferred size so relayout clamps constraints without forcing the File Changes pane to its maximum.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* sessions: mock lifecycle for changes view fixture
Register a no-op ILifecycleService so the full Changes view component fixture can instantiate ViewWelcomeController under the strict fixture instantiation service.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* sessions: add setting to show empty default groups (Pinned, Chats) in the sessions list
Add `sessions.list.showEmptyDefaultGroups` (default true) to control whether the
empty Pinned and Chats default groups are shown in the sessions list. When disabled,
the always-visible empty sections are hidden until they contain sessions. The list
re-renders live when the setting changes.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* sessions: set APPLICATION scope on showEmptyDefaultGroups setting
Fixes the unused `ConfigurationScope` import (noUnusedLocals) and aligns the
setting scope with nearby Sessions settings.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* sessions: use window scope for showEmptyDefaultGroups setting
Remove the APPLICATION scope (defaulting to WINDOW) and drop the now-unused
ConfigurationScope import.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Pass the Copilot CLI session label through the Agents Window delete flow into the Git worktree removal confirmation so dirty worktree prompts show which session owns the worktree.\n\nFixes #324220\n\nCo-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Review changes (P1): add overlayPathIntoTree git primitive
Add `IAgentHostGitService.overlayPathIntoTree(base, path, source)` which
builds a new tree equal to `base` with a single repo-relative path replaced
by (or removed to match) the content in `source`, using a throwaway
GIT_INDEX_FILE so the user's real index is untouched.
This is the file-level building block for the upcoming reviewed-ref based
"review changes" feature: mark reviewed = overlay from the working-tree
snapshot; unmark = overlay from the baseline tree.
Includes the `parseSingleLsTreeEntry` helper and real-git integration tests
covering modified, added, and removed paths, plus the non-git no-op case.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Review changes (P2): extract shared Branch Changes baseline resolver
Extract the Branch Changes baseline resolution so the changeset service and
the upcoming review service cannot drift on which baseline they use:
- Add `IAgentHostGitService.resolveBranchBaselineCommit(workingDirectory,
baseBranch?)` which resolves the merge-base commit-ish the Branch Changes
diff is anchored on (origin/<base> preference, HEAD fallback, empty-tree
fallback). `computeSessionFileDiffs` now delegates to the same private
`_resolveBranchMergeBaseCommit` helper -- pure refactor, no behavior change.
- Add the pure `resolveDiffBaseBranchName(persisted, gitState)` helper for the
base-branch-name precedence and use it from the changeset service.
Adds unit tests for both pure helpers and real-git integration tests for
`resolveBranchBaselineCommit`; existing `computeSessionFileDiffs` tests still
pass.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Review changes (P3): add reviewed-ref review service core
Add `IAgentHostReviewService` and its node implementation, tracking which
files in a session's Branch Changes the user has reviewed as a session-private
synthetic git ref (`refs/agents/<sid>/reviewed`) whose tree snapshots the
reviewed content.
- `markFileReviewed` overlays the file's current working-tree content into the
reviewed tree; `unmarkFileReviewed` resets it to the baseline content. Each
action appends a parent-chained commit (first parent = baseline commit) and
advances the ref; no-op mutations are skipped so the chain doesn't grow.
- `getReviewedPaths` derives review status from git trees: reviewed = Branch
Changes files whose reviewed-tree content matches the working tree. Editing a
reviewed file therefore auto-unreviews it.
- Mutations/reads are serialized per session; the reviewed ref is deleted on
session data disposal. Operations no-op when not in a git work tree (a future
milestone adds the non-git DB fallback).
Also adds the `diffTreePaths` git primitive used to compute review status, and
wires the service into the agent-host node and server entry points. Covered by
real-git integration tests.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Review changes (P4): wire the review operation handler + provider
Add `AgentHostReviewFileOperationHandler` (mark/unmark, one instance per
direction) and `AgentHostReviewOperationContribution`, advertising the
`mark-as-reviewed` / `mark-as-unreviewed` resource-scoped operations for the
Branch Changes changeset and delegating to `IAgentHostReviewService`.
The handler resolves the session's working directory and base branch (via the
shared `resolveDiffBaseBranchName`) so review status is keyed on the same
baseline the Branch Changes diff uses.
Plumb the review service into `AgentService`'s inner DI (mirroring the
checkpoint service, defaulting to `NULL_REVIEW_SERVICE`) and register the
contribution. Covered by handler unit tests using a fake review service.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Review changes (P5): surface per-file review status on the Branch changeset
Populate `ChangesetFile._meta.reviewed` for the Branch Changes changeset so the
client can render reviewed/unreviewed affordances per file:
- Inject `IAgentHostReviewService` into the changeset service and, when
publishing the Branch changeset, look up the reviewed repo-relative paths and
set `_meta.reviewed` per file (keyed by the file id's repo-relative path).
- Extract the base-branch resolution into a shared `_resolveBranchBaseBranch`
helper reused by the diff computation and the review-status lookup.
- After a mark/unmark, the operation handler triggers `refreshBranchChangeset`
so the updated `_meta.reviewed` is republished (the working tree is unchanged
by a review toggle, so no file-watcher event would otherwise fire).
Adds a reusable `createNoopChangesetService` test helper, updates the handler
test to assert the refresh, and threads the new dependency through existing
agent-host test fakes.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Review changes (P6): copy the reviewed ref on session fork
Add `IAgentHostReviewService.copyReviewedRef(source, target, workingDirectory)`
which points the forked session's reviewed ref at the same commit as the
source's, so a fork starts with the parent's review progress. No-op when the
source has no reviewed ref or the directory is not a git work tree.
Wire it into the Copilot session-fork path (best-effort, after the forked
session's database is copied), and inject the review service into CopilotAgent.
Covered by a real-git integration test.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* More refactoring/cleanup
* More changes to get things working
* Fix the actions in the toolbar
* Collapse multi-file diff item that is reviewed
* Remove precondition
* Fix tests + pull request feedback
* Fix hygiene
* Skip integration tests for now
* Make the UI snappier
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Kimi models (kimi-k2.6, kimi-k2.7-code) require temperature=1 and
top_p=0.95. Override these in customizeCapiBody so the values are
forced on all outbound CAPI requests regardless of what the client
would otherwise send, across agent/ask/edit modes and streaming and
non-streaming paths.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
fix: zero-pad percent-encoding for code points below 0x10 in UriTemplate
pctEncode emitted '%' + chr.toString(16) without padding, so a code point < 0x10 produced a single-digit escape (e.g. tab -> %9, newline -> %0A becomes %A, CR -> %D) instead of the RFC 3986/6570 two-digit form. The result is a malformed URI that decodeURIComponent rejects with "URI malformed". UriTemplate is used to resolve MCP and agent resource URIs, where a variable value containing a control character would yield a broken URL.
Zero-pad to two hex digits with padStart(2, '0'); this is a no-op for code points >= 0x10, so existing escapes (%20, %21, ...) are unchanged. Adds a regression test.
* sessions requiring input
* Dismiss blocked-sessions dropdown + context-specific requires-input messages
- Close the dropdown on Escape or an outside click (contextView onDOMEvent)
- Show a specific titlebar message when all blocked sessions share one reason (terminal approval, failing CI, question, unresolved comments); fall back to the generic 'N sessions require input' for a mix
- Animate the first requires-input appearance (preserve the blink class across redundant re-renders)
Removes the standalone "Subagents" dropdown above the chat input and
instead surfaces a chat's subagents as a separate group at the bottom of
the Conversations menu, scoped to the currently-active chat.
- Delete SessionAgentsControl and its CSS; drop it from ChatView.
- SessionConversationsMenuContribution now registers the active chat's
subagents in a `2_subagents` group below the session's chats.
- Add SessionActiveChatHasSubagentsContext so the Conversations menu
surfaces even when the parent is the only committed chat.
- Show the chat tab strip as soon as the session has any subagent, so
the Conversations menu moves to the tab bar.
- Add a regression test asserting a spawned subagent chat is resolvable
from the inline pill resource via parseChatUri (the Open-Subagent
contract), guarding against the pill/catalog identity desyncing.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* theme: add foreground color for problems warning icon in 2026 Light theme
css: remove opacity adjustments for warning and info labels in chat widget
* theme: update foreground color for problems warning icon in 2026 Light theme
Co-authored-by: Copilot <copilot@github.com>
---------
Co-authored-by: mrleemurray <mrleemurray@users.noreply.github.com>
Co-authored-by: Copilot <copilot@github.com>
The chat list rows span the full viewport width while the item container is centered with a max-width, leaving gutters on either side. The base list stylesheet sets cursor: pointer on rows, so the gutters showed a pointer cursor even though the item container uses cursor: default. Force default cursor on chat list rows so the gutters match.
Fixes#324173
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Some deps ship their native binary in a per-platform package declared as an
*optional* dependency of a small base package (e.g. `@openai/codex` ->
`@openai/codex-<platform>-<arch>`, `@anthropic-ai/claude-agent-sdk` ->
`@anthropic-ai/claude-agent-sdk-<platform>-<arch>`). npm does not fail when an
optional dependency can't be installed, so a transient hiccup can leave the base
package present but the per-platform package missing — and that broken tree then
gets frozen into the shared node_modules cache and served to every consumer
(see #323881).
Add build/azure-pipelines/common/checkNativeOptionalDeps.ts and run it after
`npm ci` in the linux, macOS and windows cache-build jobs (before the cache is
saved). For each configured base package that is installed, it asserts the
matching `<base>-<platform>-<arch>` package exists, and fails the job otherwise
so a poisoned cache is never saved.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Remove the system-wide keybindings first-run dialog
The first-run notice could appear in multiple windows at once on startup, and
the single-window election meant to prevent that was racy across concurrently
syncing renderers. Rather than harden the election, remove the dialog entirely:
the feature is always on and users who opt a keybinding into "systemWide" know
what they are doing.
This deletes the whole notice path, which existed only to serve the dialog:
- renderer: drop the first-run notification, the acknowledged-storage gate, and
the IDialogService/IStorageService deps; sync() now just warns about ignored
when-clauses and pushes to the main process.
- main process: drop the elected-window bookkeeping so INativeSystemWideKeybindingResult
only reports failures.
- update the systemWide keybindings.json schema description and drop the
now-obsolete election unit tests.
Global registration and trigger routing are unchanged.
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
* Add a specification doc for system-wide keybindings
Co-locate an architecture/spec document next to the renderer contribution so
future work has the full feature context (user contract, renderer<->main-process
flow, the systemWide flag plumbing, design rationale, tests, and gotchas).
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
