Route both synthesized failure descriptions through @vscode/l10n with
placeholders for the provider code and diagnostic details, matching the
localized endpoint error pattern in imageLimits.ts. These strings reach the
user as the BYOK failure reason, so a non-English install should not receive
untranslated text. The bracketed identifiers stay verbatim so they remain
greppable and pasteable into a provider support request.
Revert the Agent Host integration test expansion. It exercised parameterless
tool schemas and tool-call continuations, which ruled out two alternative
causes while investigating, but no production tool handling changes here and
that coverage does not validate this fix.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
A provider can end a Responses stream with a terminal event whose error
object omits the code and message the API contract requires. Serializing
that object produced {"code":0,"message":"","metadata":{}}, which the BYOK
endpoint promotes to the entire user-facing reason, so an outage and a
malformed request looked identical and neither users nor maintainers could
tell them apart.
Describe such failures instead, naming the terminal event, response status,
and response id so the failure stays correlatable with the provider, and
omit absent metadata keys so serialization cannot collapse them to an empty
object. Keep the fetcher's original reason when a stream error carries no
message, so a hollow struct never replaces an actionable one.
The mapping predates the reports; the Agent Host BYOK proxy moving from
Chat Completions to Responses in 1.132.0 is what first exposed it in the
Agents Window. This restores diagnosability rather than stopping the
upstream failure, so it does not close the report on its own.
Related to #330408
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* implements rich link presentation in chats
* Allows settings to be set by experiments
* Fix rich link CI configuration
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: b8949987-7bbf-43c2-a7bb-ee6450ac74c7
---------
Copilot-Session: b8949987-7bbf-43c2-a7bb-ee6450ac74c7
* Revert to showing all context size options
Removes the `github.copilot.chat.preferLongContext.enabled` setting and
reverts to always showing both the default and long-context options in the
model picker. Also removes the now-dead `freeLongContext` plumbing that the
setting gated.
Reverts:
- https://github.com/microsoft/vscode/pull/322950
- https://github.com/microsoft/vscode/pull/323116
- https://github.com/microsoft/vscode/pull/324650
- https://github.com/microsoft/vscode/pull/328628
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Add context-size picker coverage for both surfaces
Addresses PR review: cover the reverted "always show both context options"
behavior for each independently implemented picker surface.
- languageModelAccess.test.ts: a free/no-surcharge endpoint publishes both
the default and full windows, with the smaller window as the default.
- copilotCliModels.spec.ts: a CLI model with defaultContextMax < maxInputTokens
and no long-context surcharge exposes both sizes, smaller as default.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Default to the longer window for free long-context models
Keeps both context-size options in every picker, but when the long-context
tier has no surcharge (free long context) the default selection — and the
no-selection behavioral fallback — is the full window rather than the smaller
default tier. Models with a long-context surcharge still default to the
smaller tier so users opt into the extra cost.
Applied consistently across all four surfaces:
- Main chat picker: getContextSizeOptions default + applyContextSizeOverride fallback
- Copilot CLI picker: buildConfigurationSchema default + resolveContextTier fallback
- Agent host: _createContextSizeConfigSchemaProperty default + getCopilotContextTier
via the restored freeLongContext flag (and hasLongContextSurcharge helper)
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Shorten context-size comments
Condense the free-long-context comments added across the picker surfaces to
concise one-liners; no behavior change.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* theme: update agent panel border colors and styles across themes
* theme: update border colors for agents in various themes
* Potential fix for pull request finding
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
* fix(theme): update agentsPanel.border to transparent
* fix(theme): set agentsPanel.border to transparent
* fix(screenshots): update image links for agent host and user data migration
---------
Co-authored-by: mrleemurray <mrleemurray@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Preserve the cleared cache state when the last observer removes itself during event notification, and cover re-observation with a regression test.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Add authSessionAccountIcon proposed API and account avatar support
Introduces a new proposed API `authSessionAccountIcon` that allows authentication
providers to supply an icon URL (typically a profile avatar) for authentication
session accounts.
Changes:
- New proposed API: `AuthenticationSessionAccountInformation.iconUrl`
- GitHub authentication extension updated to fetch and provide user avatar URLs
- Activity bar and global composite bar updated to display account avatars
- Authentication service extended to propagate icon information
* Address Copilot review feedback
- Use removeAttribute('src') instead of empty string to avoid spurious requests
- Add alt='', aria-hidden='true', draggable=false to avatar img for accessibility
- Update iconUrl in addOrUpdateAccount when provider supplies/changes it
- Fetch avatarUrl for existing sessions that are missing iconUrl
* Address review feedback: account icon as Uri, avatar setting, Agents window consolidation
- Change AuthenticationSessionAccountInformation.iconUrl (string) to icon (Uri)
per review feedback, and use URI in the internal workbench type
- Revive the icon URI at the RPC boundaries (MainThread/ExtHost), typing the
proxies as Proxied<T>
- Persist the fetched avatar in stored GitHub auth sessions so it is not
refetched on every read
- Add workbench.accounts.showAvatar setting to show/hide account avatars
- Agents window: prefer the authentication session's account icon over the
hardcoded github.com avatar URL pattern and honor the new setting
* Fix Compile & Hygiene: tab indentation in extensionsApiProposals and remove unused import
* Fix DynamicAuthProvider test mock to match Proxied proxy typing
* auth - improve account avatar support
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Dmitriy Vasyura <dmitriv@microsoft.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Forward adaptive and budget-based thinking capabilities from custom model
configuration into endpoint metadata. Preserve the per-request thinking flag
across the extension-contributed language model boundary so Messages requests
can activate the configured mode.
Refs #330712
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
CAPI now returns `max_prompt_tokens` and `cache_read_price` inside
`billing.token_prices.<tier>`, replacing `context_max` and `cache_price`.
`normalizeTokenPrices` only read the old names, so
`tokenPricing.default.contextMax` came back undefined and
`getContextSizeOptions` bailed on its first guard, dropping the Context Size
control from the model picker entirely.
The budget side of that contract kept working, which turned a missing dropdown
into a billing problem: `modelMetadataFetcher` still raises the prompt budget to
the full context window whenever a `long_context` tier is present, on the stated
assumption that `defaultContextMax` holds users at the default tier. With
`contextMax` undefined, requests ran unclamped against the full window and
`applyContextSizeOverride` had nothing to clamp to.
Since this is a server-side rename, older clients are affected too, which is why
rolling back did not help. The agent host normalizer in `agentModelPricing.ts`
already accepts both spellings, which is why the Copilot harness kept the control
while the in-editor path lost it. Accept both here as well: this normalizer is
shared by CAPI `/models`, the `@github/copilot` SDK and the cloud agents
endpoint, which move on independent cadences.
Fixes#330481
Emit an explicit object schema for parameterless function tools so strict
OpenAI-compatible Responses endpoints accept the request.
Fixes#330610
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* markdown: refactor: use setTaskCheckboxChecked for task toggles
The webview hand-rolled the task checkbox source edit: it looked up the list
item offset, computed the '[ ]' range and applied a StringEdit itself. That
logic now lives in EditorModel.setTaskCheckboxChecked, so delegate to it.
This also fixes toggling in read-only mode. The old handler bailed out on
model.readonlyMode and then routed through applyEdit, which is itself
read-only gated, so clicking a rendered checkbox in read-only mode did
nothing. Read-only in this editor means markers hidden and no text editing
while selection and copy still work - a rendering and interaction mode
rather than a document permission - so setTaskCheckboxChecked deliberately
bypasses that gate while applyEdit, applyEditForSelection and
materializePendingParagraph stay gated.
Requires a @vscode/markdown-editor release containing
setTaskCheckboxChecked (microsoft/vscode-packages#253).
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: e9ec8741-eb31-42f3-9e0c-13e2add8e02d
* markdown: chore: update @vscode/markdown-editor to 0.0.2-70
Picks up `EditorModel.setTaskCheckboxChecked`, which the task checkbox
handler in `markdown-editor-src/editor.ts` delegates to.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: e9ec8741-eb31-42f3-9e0c-13e2add8e02d
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: e9ec8741-eb31-42f3-9e0c-13e2add8e02d
* Revert "Revert new TAS endpoint changes (#330175)"
This reverts commit f30e3f3600.
* Re-land new TAS assignments endpoint with proxy-aware transport + tas-call telemetry
* bump remote + remote/web to tas-client 0.4.3
* Add tests and feedback update
* feat: add modern tab colors and update styles for improved UI theming
Co-authored-by: Copilot <copilot@github.com>
* feat: enhance modern UI with updated tab backgrounds and improved activity indicators
Co-authored-by: Copilot <copilot@github.com>
* feat: add modern activity bar colors and update styles for improved UI theming
Co-authored-by: Copilot <copilot@github.com>
* feat: enhance modern UI with new foreground colors for activity bar and tabs
Co-authored-by: Copilot <copilot@github.com>
* feat: update modern activity bar colors for improved UI consistency
* feat: enhance modern UI theming with updated color definitions and improved tab styles
Co-authored-by: Copilot <copilot@github.com>
* feat: add modern tab action background colors for improved UI theming
Co-authored-by: Copilot <copilot@github.com>
* feat: update modern activity bar colors across themes for improved UI consistency
* feat: enhance modern UI theming with new selected action background for tabs and session view
Co-authored-by: Copilot <copilot@github.com>
* fix: add missing newline at end of sessionBarStyles test file
---------
Co-authored-by: mrleemurray <mrleemurray@users.noreply.github.com>
Co-authored-by: Copilot <copilot@github.com>
Avoid treating unmatched virtual resources as local filesystem paths when
looking up repository remotes.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Remove the team-only value restriction from the hidden advanced Xtab nLinesAbove and nLinesBelow settings. Extend external-user coverage with the requested 0 and 7 values.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 97f1135d-4a33-4139-ab2c-9cb8045ece70
Propagate Responses summary-part completion markers through the language model thinking stream so transport chunks remain combined without merging distinct semantic summaries.\n\nCo-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Keep transport-level thinking deltas in one reasoning summary entry while preserving explicit multi-part summaries. This prevents Copilot CLI from rendering each DeepSeek reasoning chunk as a separate line.\n\nFixes #329873\n\nCo-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
copilot: fix: allow external users to configure inline edit settings
Remove the team-only value restriction from selected hidden advanced inline edit settings while preserving their keys, defaults, validators, and experiment behavior. Add coverage that verifies an external user can configure all ten settings.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 97f1135d-4a33-4139-ab2c-9cb8045ece70
* Revert "New TAS assignments endpoint updates (lifecycle, readiness, disposal) (#329736)"
This reverts commit c780ea9613.
* Revert "Add new exp TAS assignments endpoint (/api/v1/assignments) alongside legacy TAS (#329653)"
This reverts commit 58dc612992.
* Fix lockfile: add MIT license fields to reverted tas-client entries
* Agent Host changes for osortega/agents/remove-all-the-code-for-backend-v1-of
* Preserve pending cloud tasks until workspace opens
Only consume cross-window task deep links after Git reports the matching repository, preventing the source window from clearing shared pending state.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Migrate cloud session state from pull request URIs
PR-backed cloud tasks are listed under a stable /task/<id> resource and report the /<prNumber> URI they were previously listed under, so archived, pinned and read state migrates forward instead of being orphaned.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Migrate the server, remote CLI, browser integration harness, and Seti update script from url.parse() to the WHATWG URL API while preserving repeated-query handling and rejecting malformed request targets.\n\nCo-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
An empty `tool_calls: []` array in a chat-completions SSE delta is truthy, so SSEProcessor entered the tool-call branch and skipped the content path, silently dropping the assistant text. Backends like vLLM attach an empty array to every content delta, which lost the entire response.
Guard the branch on `tool_calls?.length` so empty arrays fall through to normal content handling.
Fixes#329963
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Bhavya UandCopilot
vritant24andCopilot
vs-code-engineering[bot]andgithub-actions[bot]
yzxcj797
Martin Check
Joaquín Ruales
Henning DieterichsandCopilot
Justin Chen
dependabot[bot]andRaymond Zhao
Dirk Bäumer
Christof MartiandCopilot
Logan Ramos
Vritant Bhardwaj
Simon SiefkeandDmitriy Vasyura
Ulugbek AbdullaevandCopilot
Vijay Upadya
Dileep Yavanmandha
Alex Ross
Osvaldo OrtegaandCopilot
Connor Peet