Microsoft Release Notes

[1.17.0] - 2026-09-03

Added

• samples: Add an end-to-end Foundry-hosted Telegram agent sample (#7883)
• agent-framework-foundry-hosting: Add explicit Agent Server or agent-owned model history selection while preventing duplicated conversation replay (#7997)

Changed

• agent-framework-core, agent-framework-foundry: [BREAKING] Restore sequence-only agent middleware inputs and remove the experimental agent-hooks core extra (#7918)
• agent-framework-core, agent-framework-foundry, agent-framework-openai: Document the same-event-loop concurrency contract for shared chat clients (#7680)
• agent-framework-devui, agent-framework-hosting-responses, agent-framework-openai: Support OpenAI SDK 3.x while retaining the existing supported floors (#7967)
• agent-framework-mistral: Migrate chat and embedding clients to the official Mistral SDK (#7960)

Fixed

• agent-framework-core, agent-framework-devui, agent-framework-foundry-hosting, agent-framework-hosting-responses, agent-framework-openai: Preserve provider refusals as marked text across history, replay, hosting, and UI conversion (#7992)
• agent-framework-ag-ui, agent-framework-core, agent-framework-devui, agent-framework-openai: Bind approvals to stable function-call occurrences while preserving legacy approval compatibility (#7988)
• agent-framework-foundry-hosting: Persist valid OAuth consent responses and restore consent state during recovery (#8006)
• agent-framework-core: Surface the underlying MCP initialization error when cancellation masks a connection failure (#7704)
• agent-framework-ag-ui, agent-framework-core: Preserve client tools and request correlation when resuming workflow-as-agent approvals (#7776)
• agent-framework-core: Project each model call's effective tool set to agent-hooks pre_model_call events (#7747)
• agent-framework-ag-ui: Preserve every parallel function result during AG-UI message conversion (#7980)
• agent-framework-devui, agent-framework-openai: Preserve Responses message boundaries, multimodal content, measured usage, and streamed response IDs in DevUI (#7968)
• agent-framework-hosting-responses: Align continuation, input, output, and media parsing with the OpenAI Responses schemas (#7966)
• agent-framework-foundry: Declare the HTTPX runtime dependency required by Azure AI Projects 2.3
• agent-framework-openai: Preserve falsey provider values, valid request content, usage details, and embedding order (#7964)
• agent-framework-foundry-hosting: Preserve JSON-safe arguments, falsey results, MCP output consistency, and shell limits in response conversion (#7965)
• agent-framework-ag-ui, agent-framework-foundry, agent-framework-openai: Preserve Responses replay metadata across stateless and provider-managed AG-UI continuations (#7906)
• agent-framework-core: Preserve compaction mutations across tool-loop calls and align thresholds and observability (#7912)
• agent-framework-gemini: Send Pydantic response formats to Gemini as response schemas (#7879)
• agent-framework-redis: Keep history-provider typing compatible across the supported Redis range (#7604)

Full Changelog: python-1.16.0...python-1.17.0

Original source

Welcome to the 1.136 release of Visual Studio Code. This release helps you finish pull requests with agents and manage agent work across complex workspaces and related chats.

• Agent Merge (Preview): Resolve review feedback, failed checks, and merge conflicts until your pull request is ready to merge.
• Multi-root workspaces (Experimental): Work with Copilot and Claude agent sessions across all folders in a multi-root workspace.
• Chat backgrounds (Experimental): Personalize the Agents window with built-in patterns or your own images.
• Chat sessions: Organize related chats in a session hierarchy and quickly see which ones need your attention.

Happy Coding!

VS Code is rolling out gradually to all users. Use Check for Updates in VS Code to get the latest version immediately.

To try new features as soon as possible, download the nightly Insiders build, which includes the latest updates as soon as they are available.

The Story of VS Code: World Premiere

Discover the story behind VS Code, from its early beginnings to the platform millions of developers use today, and the community that helped shape it along the way.

Premiere: September 4 at 8:00 AM PT. Join us!

Agents

Multi-root workspaces in editor window (Experimental)

Settings: chat.agentHost.copilotAgent.multiRootEnabled, chat.agentHost.claudeAgent.multiRootEnabled

Copilot and Claude agent sessions in the editor window Chat view support multi-root workspaces.
This capability is currently scoped to the editor window.
Agent hooks remain scoped to a single workspace folder. If hooks are detected in multiple folders, VS Code prompts you to select the primary folder from which to load them.

Redesigned new-session input

Start delegated work with less setup in the redesigned new-session input. The updated experience brings the prompt, model selection, workspace selection, and other session controls together in one layout.

Improved workspace resolution

Agents can resolve workspaces by their project name in addition to absolute paths and workspace URIs. Session tools also preserve project URIs and all working directories for multi-root workspaces.

As a result, you can make requests such as "run this in the vscode workspace" without providing a full path. If multiple workspaces have the same name, the agent reports the possible matches instead of silently choosing one. Remote workspace URIs are supported as well.

Navigate related chats and sessions

Keep related agent work organized and move between sessions and chats from the sessions list in the Agents window. Chats appear as children of their parent session, so you can understand which chats belong together without managing a collection of unrelated sessions.
Each chat row shows its own title, status, and pending approvals, so you can see which chat needs your input. Expand or collapse the hierarchy, and open, rename, move, or delete individual chats directly from the tree.
When an agent delegates independent work to multiple chats, each created chat gets a meaningful title and appears in this hierarchy.

The new session or chat is placed close to its source, and the receiving request includes a source link such as Sent by another session or Sent from another chat. Select the link to return to the exact session or chat that initiated it.

Readable breadcrumbs for session files

Files created in the internal session state directory previously showed internal session identifiers in editor breadcrumbs. Breadcrumbs now use stable provider and session labels, making it easier to identify the file location without exposing implementation details.

Chat backgrounds in the Agents window (Experimental)

Settings: chat.agentSessions.preferredDarkBackgroundImage, chat.agentSessions.preferredLightBackgroundImage, chat.agentSessions.backgroundImageLayout

Personalize the Agents window with a decorative chat background: either a theme-aware pattern of built-in VS Code icons or an image of your own.
Run Chat: Set Background... to choose between the Codicons pattern and an image from your machine. The five images you used most recently are offered under Recently Used, and that list is kept on this machine only.
When you bring your own image, run Chat: Change Background Layout... to place it. Eleven layouts are available: Repeat, Stretch, Center, and each edge and corner. Moving through the list previews each layout in place, so you can judge the result before committing to it. Chat: Clear Background returns to the plain surface.
Dark and light themes keep separate backgrounds. Every dark theme shares chat.agentSessions.preferredDarkBackgroundImage and every light theme shares chat.agentSessions.preferredLightBackgroundImage, so switching between a dark and a light theme swaps the background along with it. High contrast themes suppress backgrounds entirely, and the three commands are unavailable there.
Chat content carries its own fill so that it stays readable over whatever sits behind it. Your request remains fully opaque, agent responses fade out through the padding on either side, and wide content such as Markdown tables and terminal output stays fully backed.
Learn more about personalizing chat.

Agent session notifications

Settings: chat.notifyWindowOnConfirmation, chat.notifyWindowOnResponseReceived

VS Code can notify you when an agent session needs your input or finishes its work. This is especially useful when you delegate work across multiple sessions, workspaces, or VS Code windows.
By default, notifications only appear when the VS Code window is not focused. You can configure notifications separately for sessions that need input and sessions that have received a response. Notifications include a direct link back to the relevant session, so selecting one focuses the correct window and opens the session that needs attention.

Agent Merge (Preview)

Setting: chat.agentMerge.enabled

Agent Merge helps you take a pull request across the finish line. It asks an agent to address review feedback, fix failed checks and merge conflicts, and rerun workflows. Agent Merge repeats this process until the pull request is ready to merge.
To try Agent Merge, enable chat.agentMerge.enabled. You can currently enable Agent Merge for a session only from the Agents window. Run Enable Agent Merge for Active Session or select the Agent Merge button in the title bar. Learn more about using Agent Merge.

Agent host

The agent host lets you connect to the same agent session from multiple VS Code windows. It runs agent harnesses in a dedicated process based on the Agent Host Protocol (AHP). The agent host's Copilot agent is powered by the Copilot SDK, which aligns the agent's behavior and functionality with the Copilot CLI, the standalone GitHub Copilot app, and other Copilot products.
We're actively developing the agent host. The following screenshot shows the Copilot harness selected for an agent host in an editor window:
Learn more in the agent host documentation and our new agent host blog post, where we share why we built the agent host, what it enables in VS Code, how the architecture and open protocol work, and workflows you can try yourself.
If you have any feedback or requests, please let us know by filing an issue.

Chat

Enterprise controls for dictation data

Administrators can manage the dictation model and language-model transcript cleanup through enterprise policies.
The new controls make it possible to require on-device transcription and disable language-model cleanup, so dictation remains available while preventing dictation data from being sent to cloud transcription or a Copilot model. Learn more about enterprise controls for dictation data.

Accessibility

Screen Reader Optimized badge in the Agents window

The Screen Reader Optimized badge in the Agents window title bar makes the active accessibility mode easier to identify. The badge appears when Screen Reader Optimized mode is enabled. Select the badge to disable this mode.

Editor experience

Layout density for the editor window (Experimental)

Settings: workbench.experimental.modernUI, window.density.layout

Fit more content in the editor window with the Compact layout density. When workbench.experimental.modernUI is enabled, you can choose between two layout densities:

• Default layout density is the same as the current editor window layout.
• Compact layout density removes the spacing between panels and reduces inner panel spacing.

This setting is available in the Layout Density section of the Settings menu and can also be set using window.density.layout.

Code editing

Word wrapping improvements

Injected text no longer pushes wrapped lines outside the editor viewport. Word wrapping takes the visual width of color decorators, inlay hint spacing, inline progress indicators, and breakpoint placeholders into account. Please have a look below for the before and after screenshots. On the picture above you can see that rgba is slightly cropped. While on the second picture it isn't.

Integrated browser

Spell check suggestions

Right-click a misspelled word in an editable field to select a suggested correction. In sessions that use persistent data storage, you can also select Add to Dictionary.

Terminal

Reduced delay when running commands

Terminal commands executed by extensions no longer incur an unnecessary delay when shell integration is ready under certain timing conditions. Users of the JavaScript debugger who hit this case will no longer experience a five-second delay when starting their programs.

Deprecated features and settings

None

Thank you

Contributions to vscode:

• @abmahdy (Ahmed Mahdy): Bound concurrency of prompt file discovery reads PR #331855
• @DanTup (Danny Tuppeny): Note that InlayHints with the same position are shown in-order PR #175525
• @davidbitton (David B. Bitton): Add spelling suggestions to the Integrated Browser context menu PR #333043
• @JeffreyCA: Update Fig spec for Azure Developer CLI (azd) PR #331727
• @juliagongms (Julia Gong): nes: apply supportsUnifiedCompletions on the default provider path PR #332802
• @koubaki: Update error message in inlineChatIntent.ts PR #329157
• @ktsoator (ktsoator): Hover: restore scrolling for long content PR #331439
• @na2co3-ftw (na2co3): Modern UI: Fix CSS specificity for tab action fading PR #332103
• @preitinger (Peter Reitinger): Update snippet.md PR #231790
• @remcohaszing (Remco Haszing):
  • Normalize end of line cursor move operation PR #296712
  • Fix out of bounds text selection with line wrapping PR #262910
  • Round custom line heights PR #298421
  • Expose the score function in Monaco editor PR #322959
• @SimonSiefke (Simon Siefke):
  • fix: memory leak in explorer viewer PR #332332
  • fix: memory leak in LSP terminal completions PR #332173
• @TheNotary: Update error message for unsupported skill attributes PR #328318
• @tisilent (xiejialong): update label and description. PR #219949
• @unsupportedpastels (Mark S.): Support reasoning effort in custom agent files PR #329263
• @weidehai (io): error correction instructions PR #249715

Contributions to vscode-emmet-helper:

• @danfiedler-msft (Dan Fiedler): Pin GitHub Actions to full-length commit SHAs PR #108

Contributions to vscode-livepreview:

• @danfiedler-msft (Dan Fiedler): Pin GitHub Actions to full-length commit SHAs PR #854

Contributions to docfind:

• @danfiedler-msft (Dan Fiedler): Pin GitHub Actions to full-length commit SHAs PR #62

Contributions to node-pty:

• @danfiedler-msft (Dan Fiedler): Pin GitHub Actions to full-length commit SHAs PR #958

Issue tracking

Contributions to our issue tracking:

• @gjsjohnmurray (John Murray)
• @saroasid-web (Saswwo)
• @zotabee (zotabee)
• @lppedd (Edoardo Luppi)
• @sandstrom (sandstrom)

We really appreciate people trying our new features as soon as they are ready, so check back here often and learn what's new.

If you'd like to read release notes for previous VS Code versions, go to Updates on code.visualstudio.com.

Original source

Memory Scan extends Microsoft Defender for Endpoint protection capabilities on Linux by enabling inspection of process memory for known malicious behaviours and memory-resident threats, providing an additional layer of protection against advanced attacks.

Memory-resident threats are increasingly challenging for security teams because they can execute directly in memory with little or no footprint on disk, making them more difficult to detect using traditional file-based scanning techniques.

Memory Scan helps improve visibility into these threats and strengthens protection against sophisticated attack methods such as in-memory malware and malicious code injection.

Available in Defender version 101.26071.0005 or later in Insiders-slow channel.

Original source

What's Changed

• .NET: Bump AWSSDK.Extensions.Bedrock.MEAI from 4.0.6.10 to 4.0.101.8 by Dependabot (@dependabot)[bot] in #7829
• .NET: Stabilize Foundry recovery tests by Roger Barreto (@rogerbarreto) in #7817
• .NET: fix: preserve Responses logprobs field by Yufeng He (@he-yufeng) in #5860
• .NET: Honor cancellation for Foundry-hosted workflow responses by Roger Barreto (@rogerbarreto) with @Copilot in #7842
• .NET: Use Responses API for hosted web search in AG-UI by Roger Barreto (@rogerbarreto) with @Copilot in #7843
• .NET: Bump Aspire.Hosting from 13.1.0 to 13.5.2 by Dependabot (@dependabot)[bot] in #7826
• .NET: Suppress false positive Zip Slip alert by SergeyMenshykh in #7858
• .NET: added Mem0Sharp integration for in-memory storage in agent samples. by Jay Khawaja (@jihadkhawaja) in #7792
• .NET: Annotate DevUI aggregator static-analysis false positives by SergeyMenshykh in #7864
• .NET: Rename CommunityToolkit.VectorData.CosmosNoSql to AzureCosmosDB by Adam Sitnik (@adamsitnik) in #7878
• .NET: chore: upgrades aspnet openapi dependency by Vincent Biret (@baywet) in #7870
• .NET: Simplify A2A function tool samples by SergeyMenshykh in #7861
• .NET: Bump Azure.AI.AgentServer.Invocations from 1.0.0-beta.5 to 1.0.0-beta.6 by Dependabot (@dependabot)[bot] in #7886
• .NET: docs: updates the contributing information for CFS users by Vincent Biret (@baywet) in #7869
• Bump CommunityToolkit.VectorData.InMemory from 1.0.0 to 1.0.1 by Dependabot (@dependabot)[bot] in #7888
• .NET: Remove retired OpenAI Assistants integration tests by Roger Barreto (@rogerbarreto) in #7896
• .NET: Simplify A2A client-server sample by SergeyMenshykh in #7891
• Bump Dapr.AI.Microsoft.Extensions from 1.18.4 to 1.18.5 by Dependabot (@dependabot)[bot] in #7889
• .NET: docs/workflow fileinput sample dotnet by Vincent Biret (@baywet) in #7913
• .NET: Add timeout for wait-for-first-completion by westey (@westey-m) in #7911
• .NET: Fix duplicate Foundry AgentHost port binding by Roger Barreto (@rogerbarreto) in #7932
• .NET: tests: removes dependency on fluent assersion because of licensing concerns by Vincent Biret (@baywet) in #7938
• .NET: docs(decisions): resolve duplicate ADR sequence numbers (0016, 0021, 0024) by John CSA (@jluocsa) in #6046
• .NET: Bump Azure.Core from 1.61.0 to 1.62.0 by Dependabot (@dependabot)[bot] in #7954
• .NET: Improve Cosmos DB Emulator startup reliability by Theo van Kraay (@TheovanKraay) in #3932
• .NET: add public API analyzers by Vincent Biret (@baywet) in #7935
• .NET: Update version for 1.20.0 release by SergeyMenshykh in #7972

New Contributors

• madanmishra1223 made their first contribution in #7705
• Yashvant Mahadev Hange (@YashvantHange) made their first contribution in #7850
• Jay Khawaja (@jihadkhawaja) made their first contribution in #7792
• Adam Sitnik (@adamsitnik) made their first contribution in #7878
• Vincent Biret (@baywet) made their first contribution in #7870
• Patel Namraa (@Namraa310806) made their first contribution in #7901
• Sweetteabittersugar made their first contribution in #7903
• Jeremy Schoemaker (@shoemoney) made their first contribution in #7837
• John CSA (@jluocsa) made their first contribution in #6046

Full Changelog: dotnet-1.19.0...dotnet-1.20.0

Original source

[1.16.0] - 2026-08-27

Added

agent-framework-core: Add configurable timeouts for waiting on the first background-agent task completion (#7908)

agent-framework-core: Allow programmatic OpenTelemetry service metadata, resource attributes, and OTLP exporter configuration (#7703)

Changed

agent-framework-foundry-hosting: Update Agent Server dependencies and expose parent FoundryToolbox constructor options (#7921)

samples: Apply ChatKit attachment lifecycle checks consistently in the end-to-end sample (#7846)

Fixed

agent-framework-ag-ui, agent-framework-foundry-hosting: Preserve backend-owned service-session snapshots and validate incremental provider continuation input (#7770)

agent-framework-anthropic, agent-framework-mistral: Preserve unmapped provider finish reasons (#7850)

agent-framework-azure-ai-search: Preserve the kinds of heterogeneous knowledge sources (#7875)

agent-framework-core: Prevent workflow checkpoints from being mutated outside storage implementations (#7847)

agent-framework-core: Discard unsafe Content fields during deep copy (#7903)

agent-framework-core: Avoid mutating caller input in SerializationMixin.from_dict() (#7901)

agent-framework-core: Keep the private agent-loop iteration marker out of provider SDK requests (#7860)

agent-framework-gemini: Preserve unmapped finish reasons and attach usage details to the correct response (#7837)

agent-framework-openai: Preserve streaming when GenAI instrumentation replaces the raw SDK response (#7705)

Original source

Release Summary

Announcements

• Deprecating the unload event. Microsoft Edge is changing the default behavior of the web platform unload event. As the rollout progresses, pages will no longer run unload event handlers unless the site explicitly permits them.
  • In Edge 152 and 153, unload handlers will stop firing by default for 60% of page loads unless the site explicitly enables them through Permissions Policy.
  • In Edge 154, the rollout will increase to 80% of page loads.
  • In Edge 155, the rollout will reach 100% of page loads.

The unload event is not a dependable way to save data, perform cleanup, or report the end of a session. Browsers and operating systems can suspend or terminate pages without firing it, and this can prevent pages from using the back/forward cache, which may make back and forward navigation slower.

Web developers should migrate to lifecycle events and APIs designed for these scenarios. The long-term direction of the web platform is to remove support for unload.

• Microsoft Edge has completed the move to a 2-week cadence for updates. We have adopted a new, 2-week release cycle for major versions. For more information, see Faster updates, enterprise-friendly schedule: the new Microsoft Edge release cycle - Microsoft Edge Blog.

Feature Updates

• Automatically unsubscribe users from notifications sent by scam and malicious sites. Microsoft Edge now helps further protect users from malicious web notifications. When a notification leads users to a site that Microsoft Defender SmartScreen blocks as a scam, phishing, or malware page, Edge automatically stops that source from sending users further notifications. Edge lets users know when this happens. Users can review and restore any of these sites anytime under edge://settings/privacy/sitePermissions/allPermissions/notifications.

Note: This is a controlled feature rollout. If you don't see this change, check back as we continue the rollout.

• Sign in to Edge with an Apple account. Users can now sign in to Microsoft Edge using an Apple account in addition to the Microsoft account from the profile menu and Edge sign-in screen. Available for Windows and macOS devices. Admins can control availability to this feature using the NonMicrosoftAccountSignInEnabled policy.

Note: This is a controlled feature rollout. If you don't see this change, check back as we continue the rollout.

• Real-time video translation retirement. Real-time video translation is being retired through a gradual rollout. Availability may vary across environments during the rollout. The LiveVideoTranslationEnabled policy will be deprecated in a future update.

• Enhanced Key Icon with Credential Details, Copy Actions, and Notes. The key icon in Edge's address bar now lets users click into any saved credential to view a detailed panel. From there, users can copy a username, reveal and copy a password, and add personal notes to each login. Keep track of security questions, account purpose, or recovery details right alongside credentials, without opening Settings or the full password manager.

Note: This is a controlled feature rollout. If you don't see this change, check back as we continue the rollout.

• Drop is retired. We're simplifying Microsoft Edge. Drop is retired in Microsoft Edge version 152.

• New Copilot Cowork policy. Copilot Cowork may perform tasks such as creating tabs, taking screenshots, and interacting with web pages. Admins can now control availability of this feature using the CopilotCoworkToolActionsEnabled policy, which corresponds to the Allow Cowork to take actions on your behalf setting in edge://settings/ai. This policy applies only when Cowork Browsing is enabled at the tenant level in the M365 admin center.

• Clarification of WebView2 DowngradeVersion policy. The DowngradeVersion policy allows admins to temporarily roll back specific applications to a previous WebView2 Evergreen Runtime version (N-1 or N-2). The policy requires an exact 4-part numeric WebView2 Runtime version, for example 151.0.2178.0. Admins can find the exact 4-part version number in the Microsoft Edge release notes for Stable Channel. Major-version-only values are not supported. If no exact matching folder is found, the policy has no effect and the runtime defaults to the BrowserExecutableFolder policy or the Evergreen runtime, which is the default auto-updating runtime.

• Update for LocalNetworkAccessRestrictionsTemporaryOptOut policy. The planned removal of the LocalNetworkAccessRestrictionsTemporaryOptOut policy has been updated. The policy is now scheduled for removal after Microsoft Edge version 156; previously it was version 152.

• Updated Copilot policy. Admins can now control availability of the video transcription feature using the EdgeEntraCopilotPageContext policy, which corresponds to the Allow Copilot to transcribe your video setting in edge://settings/ai.

Original source

This cumulative update for Windows 11, version 26H1 (KB5120996), includes production-quality improvements.

Announcements and messages

This section provides key notifications related to this release, including announcements, change logs, and end-of-support notices.

Highlights

This update is available through two release phases: gradual rollout and normal rollout. A gradual rollout delivers an update in phases, so features reach devices over time instead of all at once, meaning availability varies by device. A normal rollout is the broad release to all eligible devices at the same time, usually when it reaches general availability (GA).

Known issues in this update

Microsoft is not currently aware of any issues with this update.

How to get this update

Before you install this update

Microsoft combines the latest servicing stack update (SSU) for your operating system with the latest cumulative update (LCU). For general information about SSUs, see Servicing stack updates.

Deployment

If you deploy dynamic updates such as this update to an existing Windows image, ensure the boot.stl file is included as part of the installation media. Failure to include the file might prevent devices from successfully starting from the installation media and can result in error code 0xc0430001.

Note

The boot.stl file is used during Secure Boot validation and must match the Windows version and architecture of the image you are updating.

To ensure the boot.stl file is included as part of the installation media, do one of the following:

• Use the Update WinPE script to update an existing Windows image. (Recommended)
• Manually copy the boot.stl file from the device Windows\Boot\EFI folder to the corresponding folder on your installation media before deploying the update.

For information about how to apply Dynamic Update packages to existing Windows images, see Update Windows installation media with Dynamic Update.

Install this update

To install this update, use one of the following Windows and Microsoft release channels.

Windows Update

Open Start > Settings > Windows Update > Advanced options > Optional updates. In the Optional updates available area, you will find the link to download and install available updates. Check for optional updates.

Original source

This cumulative update for Windows 11, version 25H2 and 24H2 (KB5120998), includes production-quality improvements.

Announcements and messages

This section provides key notifications related to this release, including announcements, change logs, and end-of-support notices.

Windows Secure Boot certificate expiration

Important: Secure Boot certificates used by most Windows devices expire starting in June 2026. Microsoft has been updating these certificates on consumer and non-managed business devices over the past several months. Devices that haven’t received the newer certificates will continue to start and operate normally, and standard Windows updates will continue to install. Updated certificates will continue to be delivered through Windows Update in the coming months. For more information, see Windows Secure Boot certificate expiration and CA updates.

Highlights

This update is available through two release phases: gradual rollout and normal rollout. A gradual rollout delivers an update in phases, so features reach devices over time instead of all at once, meaning availability varies by device. A normal rollout is the broad release to all eligible devices at the same time, usually when it reaches general availability (GA).

If you installed earlier updates, your device downloads and installs only the new updates contained in this package.

Known issues in this update

Microsoft is not currently aware of any issues with this update.

How to get this update

Before you install this update

Microsoft combines the latest servicing stack update (SSU) for your operating system with the latest cumulative update (LCU). For general information about SSUs, see Servicing stack updates.

Deployment

If you deploy dynamic updates such as this update to an existing Windows image, ensure the boot.stl file is included as part of the installation media. Failure to include the file might prevent devices from successfully starting from the installation media and can result in error code 0xc0430001.

Note

The boot.stl file is used during Secure Boot validation and must match the Windows version and architecture of the image you are updating.

To ensure the boot.stl file is included as part of the installation media, do one of the following:

• Use the Update WinPE script to update an existing Windows image. (Recommended)
• Manually copy the boot.stl file from the device Windows\Boot\EFI folder to the corresponding folder on your installation media before deploying the update.

For information about how to apply Dynamic Update packages to existing Windows images, see Update Windows installation media with Dynamic Update.

Install this update

To install this update, use one of the following Windows and Microsoft release channels.

Windows Update

Available

Next Step

Open Start > Settings > Windows Update > Advanced options > Optional updates. In the Optional updates available area, you will find the link to download and install available updates. Check for optional updates

File information

For a list of the files provided in this update, download the file information for cumulative update KB5120998.

For a list of the files provided in the servicing stack update, download the file information for the SSU (KB5120997) - version 26100.9274.

Related topics

Windows monthly updates explained

Description of the standard terminology used for Microsoft software updates

Microsoft Store for Business and Education with Configuration Manager

Get updates for apps and games in Microsoft Store

Original source

Welcome to the 1.135 release of Visual Studio Code. This release helps you continue agent sessions across applications, get a second opinion on agent work, and understand chat usage while working in a more streamlined Agents window.

• External agent sessions: Continue recent Copilot or Claude agent sessions from other applications in VS Code.
• Rubber Duck (Experimental): Get a second opinion from a complementary model to surface missed details and edge cases.
• Agents window UX improvements: Work with a streamlined side layout, simplified session controls, and session information that is easier to find.
• Detailed chat usage: View a per-model breakdown of input, cached input, and output tokens for each chat turn.

Happy Coding!

VS Code is rolling out gradually to all users. Use Check for Updates in VS Code to get the latest version immediately.

To try new features as soon as possible, download the nightly Insiders build, which includes the latest updates as soon as they are available.

Agents

Agent host

The agent host lets you connect to the same agent session from multiple VS Code windows. It runs agent harnesses in a dedicated process based on the Agent Host Protocol (AHP). The agent host's Copilot agent is powered by the Copilot SDK, which aligns the agent's behavior and functionality with the Copilot CLI, the standalone GitHub Copilot app, and other Copilot products.

We're actively developing the agent host. The following screenshot shows the Copilot harness selected for an agent host in an editor window:

Learn more from our VS Code Agent Host documentation and the video below. If you have any feedback or requests, please let us know by filing an issue.

See it in action in our Agent Host introduction YouTube video.

Continue external agent sessions in VS Code

Setting: chat.agentSessions.showExternal

The Sessions list in VS Code can now show recent Copilot or Claude agent sessions that you created in other applications. By default, VS Code shows up to two recently updated external sessions. Select a session from the Sessions list to view the conversation and continue it in VS Code with your Copilot subscription.

When you open an external session, a banner at the top of the chat lets you configure how many external sessions appear in the Sessions list. You can also use the External submenu in the Sessions list filter to choose which external sessions are shown. Change this preference at any time with the chat.agentSessions.showExternal setting.

Rubber Duck (Experimental)

Rubber Duck is an experimental feature that allows you to get a second opinion from a complementary model on the agent's work. It helps surface missed details or edge cases. You can use Rubber Duck by invoking the /rubber-duck command in a Copilot agent host session.

Learn more about Rubber Duck in GitHub Copilot CLI.

Single-pane side layout is now the default

Setting: sessions.layout.singlePaneDetailPanel

In the previous release, we introduced the single-pane layout. In this layout, session details and editors are located in a single side pane, with a shared tab bar next to chat. The single-pane layout is now enabled by default for the Agents window on desktop.

This release also improves the layout:

• Diffs use a side-by-side view when space permits and switch to an inline view when the side pane becomes too narrow. Use Always Show Inline Diff from the editor title menu to keep diffs inline at every width.
• The action bar is less crowded. Editor-specific actions for diffs, view modes, code review, and attachments move to the editor title area, while the shared header focuses on showing or hiding Details.

To use the classic layout, disable sessions.layout.singlePaneDetailPanel and reload the window.

Simplified session controls and information

The session header is less crowded, so you can identify the active session more easily and focus on the conversation.

The session title has a prominent position, while an overflow menu next to the title groups actions for creating a chat and pinning the session. Search remains available in the Sessions list. When a session contains multiple chats, chat tabs replace the single-chat header.

Session information moves directly above the chat input, where it is easier to find while you work. Pills can show changes, pull requests, issues, browsers the agent is interacting with, and artifacts from the session. For example, the Changes pill shows live file and diff counts and opens the complete set of session changes.

Right-click an individual pill to open a context menu and choose which pill types are visible. The Changes pill remains visible whenever the session has changes.

Chat

Editor-style sticky scroll for chat (Experimental)

Settings: chat.stickyScroll.enabled, chat.experimental.stickyScroll.enabled

Chat sticky scroll lets you keep the current prompt visible as you scroll through and review long responses. We've further refined the behavior to make it more consistent with sticky scroll in the editor. Enable both settings to try the redesigned experience.

View detailed chat turn usage

To give you better insight into your chat usage, we've redesigned the chat response footer. When you hover over it, the footer shows a per-model breakdown of the input, cached input, and output tokens used in that chat turn.

Sandboxing for the local agent harness

We previously rolled out sandboxing to 50% of users to validate it on a larger scale and in real-world use cases. While we didn't identify a specific blocking issue, continuing the rollout would likely require more support and follow-up work at a time when we want to preserve focus on higher-priority investments, especially in the area of the agent host and the Copilot harness. We've therefore returned the default rollout to 0% for now.

Sandboxing for the local agent harness remains available as an opt-in feature through the UI, so users who want to try it can still enable it.

Deprecated features and settings

None

Thank you

Contributions to vscode:

• @a-stewart (Anthony Stewart): Rename leftover respectAutoSaveConfig variable to isRefactoring PR #160703
• @bstee615 (Benjamin Steenhoek): Add eagerness option for diffpatch prompt PR #327544
• @cipheraxat (Akshat Anand): fix: center Modern UI panel title tabs in the 32px header PR #331612
• @danyalahmed1995 (Danyal Ahmed): Fix case-insensitive aggregated basename glob matching PR #316387
• @dzsquared (Drew Skwiers-Koballa): add mcp server key as description in tool picker PR #325003
• @guimmd2 (Guilherme Menezes Magalhães): Fix package.json hover metadata broken in npm 12+ PR #327951
• @jachinsamuel (Jachin Samuel): docs: remove dead Gitter badge (service shut down June 2023) PR #322702
• @jadefr (Jade Ferreira Vieira): Fix file URL to path conversion in html-language-features esbuild script PR #328557
• @jainampatel27 (Jainam Patel): Fix typo in selectionHighlightMaxLength description PR #296427
• @juliagongms (Julia Gong): nes: add optimized PatchBased02 prompt strategy PR #332018
• @n-gist (n-gist): fix languages.getDiagnostics() problem-matchers diagnostics duplication PR #290278
• @rfeltis (Ralph Feltis):
  • Remove Agents window startup A/A experiment trigger PR #331559
  • Revert chat quota trajectory nudge PR #331401
• @RyanEwen (Ryan Ewen): Do not present a failed tool call as a successful one PR #330707
• @SimonSiefke (Simon Siefke):
  • fix: memory leak in markersTable PR #327885
  • fix: memory leak in mainThreadDocumentsAndEditors PR #331170
  • fix: memory leak in settings preview indicator PR #331990
• @srikanthananthula63053 (srikanthananthula):
  • fix: use fresh service accessor when lazily initializing chat attachment context (fixes #329610) PR #331416
  • Fix section checkbox state when all items are unchecked PR #331419
• @TheRealAlexxx (alexxx): Fix typo in Settings UI description for editor.selectionHighlightMaxLength PR #332162
• @zainnadeem786 (Zain Nadeem):
  • Await Workspace Trust transition completion in setUrisTrust() PR #328626
  • Fix PowerShell quoting for runInTerminal environment values PR #331753

Contributions to vscode-windows-process-tree:

• @danfiedler-msft (Dan Fiedler): Pin GitHub Actions to full-length commit SHAs PR #91

Issue tracking

Contributions to our issue tracking:

• @gjsjohnmurray (John Murray)
• @xguarch (Xavier Guarch)
• @homeworld614 (homeworld614)
• @johnnydecimal (Johnny Noble)
• @wenma531 (noreply)

We really appreciate people trying our new features as soon as they are ready, so check back here often and learn what's new.

If you'd like to read release notes for previous VS Code versions, go to Updates on code.visualstudio.com.

Original source

Updates released between August 11, 2026, and August 25, 2026.

Excel

• Use Python when Editing with Copilot in Excel [Windows, Mac, Web]

Edit with Copilot helps you work with Python in Excel by executing Python code for advanced analysis, automation, and data transformation with results outputted directly in your workbook.

Details:

What changed: You can now use Edit with Copilot to perform advanced data analysis (statistics, simulations, advanced visualizations etc.) with your workbook data. Existing security and execution controls continue to help manage how code runs.

Why: Python is widely used for data analysis, visualization, and automation. Bringing Copilot-assisted Python editing into Excel helps users move from intent to working analysis faster without switching tools.

Try this:

1. Open an Excel workbook with data you want to analyze.
2. Open Edit with Copilot.
3. Ask Copilot to complete a task like summarizing trends, cleaning data, or creating a visualization with Python.
4. Review the output and inspect the results in Excel.

Why this matters: This makes advanced analysis more approachable by pairing Python’s flexibility with Copilot’s assistance and Excel’s familiar workspace.

Business impact: Teams can accelerate reporting, analysis, and repeatable data workflows in Excel, helping reduce manual effort and improve consistency.

Personal impact: You can complete more advanced data tasks in Excel with Copilot’s help.

Microsoft 365 admin center

• Organizational Messages now supports Hybrid-joined Devices [Web]

Organizational Messages now supports Hybrid-joined Devices.

Roadmap ID: 503564

Details:

What changed: Previously, Organizational Messages were limited to devices fully joined to Azure Active Directory or on-premises Active Directory. Now, hybrid Azure AD joined devices can receive Organizational Messages, expanding device coverage. This update improves message delivery consistency across device management environments.

Why: Supporting hybrid-joined devices ensures that organizations using both on-premises and cloud identity management can communicate important messages uniformly. This reduces gaps in message reach and improves compliance.

Try this:

1. Open the Microsoft 365 admin center.
2. Navigate to the Organizational Messages section.
3. Create or update a message and target hybrid Azure AD joined devices to verify delivery.

Why this matters: This change ensures all managed devices receive critical organizational communications regardless of their join type.

Business impact: IT teams can now rely on Organizational Messages to reach hybrid device fleets without additional configuration or tools.

Personal impact: Users on hybrid-joined devices receive timely organizational updates, reducing confusion and support requests.

Microsoft 365 Copilot

• Viva Engage private content in Microsoft 365 Copilot [Web]

Viva Engage content from private communities and events will be used as grounding source for Microsoft 365 Copilot. When a user queries in Microsoft 365 Copilot, they will only be able to see content they are privileged to access.

Roadmap ID: 515144

Details:

What changed: Microsoft 365 Copilot includes private Engage community and event content when responding to queries. Previously, Copilot did not incorporate private community data. Users only see content they have permission to access, maintaining security and privacy.

Why: Including private community content ensures Copilot provides more relevant and comprehensive answers while respecting access controls.

Try this:

1. Open Microsoft 365 Copilot.
2. Ask a question related to your private Engage communities or events.
3. Review the response that includes content you are authorized to view.

Why this matters: This change enhances Copilot’s relevance by incorporating private organizational knowledge securely.

Business impact: Teams gain improved insights from private discussions without compromising data security.

Personal impact: You receive more accurate answers that include your private community knowledge, improving productivity.

• Updated Copilot Notebooks UX [Web]

Users will find an updated, streamlined UX flow within Copilot Notebooks.

Roadmap ID: 516042

Details:

What changed: The Copilot Notebooks user experience has been revamped with a streamlined flow for opening items and navigating the product. Previously, users faced a more complex and less cohesive interface. The new design simplifies common tasks and enhances consistency across the product.

Why: Simplifying the user interface reduces friction and helps users work more efficiently within Copilot Notebooks.

Try this:

1. Open Copilot Notebooks from the Microsoft 365 app launcher.
2. Use the updated navigation pane to browse notebooks and sections.
3. Open and edit notebook items with the new streamlined controls.

Why this matters: A simpler, more cohesive interface helps users focus on content creation and reduces time spent on navigation.

Business impact: Teams experience smoother collaboration and faster access to notebook content, improving productivity.

Personal impact: You spend less time navigating and more time working on your notebooks.

• Copilot Chat available when using Copilot Search [Windows, Web]

Copilot Chat will be available for Microsoft 365 Copilot users from the side pane on the right-hand side when using Copilot Search in the Microsoft 365 Copilot app. This allows users to engage with Copilot while browsing universal search without switching pages or losing context.

Roadmap ID: 537281

Details:

What changed: Copilot chat is now accessible from the right-hand side pane during Copilot Search for users with the AI SKU. Previously, users had to switch pages to use Copilot chat, interrupting their workflow.

Why: Integrating chat in the side pane keeps Copilot accessible alongside search results, improving multitasking and reducing context switching.

Try this:

1. Open Copilot Search in the Microsoft 365 Copilot app.
2. Engage with your search results or ask questions in the search box to open Copilot chat.
3. Interact with Copilot chat while browsing search results.

Why this matters: This integration helps users maintain focus by combining search and chat in one view.

Business impact: Teams can work more efficiently by accessing AI assistance without disrupting their search workflows.

Personal impact: You save time by getting AI help without switching screens or losing your search context.

• Open Outlook emails within Copilot Chat [Windows, Mac, Web]

You can now open Outlook emails directly within any full-app Microsoft 365 Copilot experience for faster browsing and reference.

Details:

What changed: When clicking on an email reference or source in Microsoft 365 Copilot apps, the email opens alongside Chat instead of requiring a separate Outlook window. Previously, users had to switch apps to view email content. This integration streamlines access to email information within the Copilot environment.

Why: This change reduces context switching and speeds up information retrieval by keeping emails accessible within the Copilot workspace.

Try this:

1. In a Microsoft 365 Copilot app, locate an email reference.
2. Click the email link to open it in Chat.
3. Browse the email content alongside your chat or tasks.

Why this matters: Quick access to emails within Copilot improves productivity and decision making by keeping relevant information in one place.

Business impact: Teams can collaborate more efficiently by referencing emails without leaving the Copilot interface.

Personal impact: You save time by avoiding app switching and can respond to emails faster within your workflow.

• Outlook Emails in Copilot Notebooks [Windows, Web]

Outlook Emails as References in Copilot Notebooks bring email content into the notebook experience, enabling users to ground Copilot in the conversations, decisions, and context that drive their work. By adding emails as knowledge sources, users can connect context from their emails directly to their projects, enriching notebooks beyond files alone and improving downstream outputs like presentations and briefs. Available in Copilot Notebooks across Microsoft 365.

Roadmap ID: 564910

Details:

What changed: Users can now add Outlook emails as knowledge sources within Copilot Notebooks across Microsoft 365. Previously, notebooks included only files and other documents. This update enables Copilot to use email content to provide richer context for outputs like presentations and briefs.

Why: Integrating emails into notebooks grounds Copilot in the full context of work conversations and decisions, improving the relevance and accuracy of generated content.

Try this:

1. Open a Copilot Notebook in Microsoft 365.
2. Select Add content and choose Outlook emails.
3. Pick relevant emails to include as references in your notebook.

Why this matters: Including emails enriches project context, helping users create more informed and connected work outputs.

Business impact: Teams can leverage email conversations directly in collaborative notebooks, enhancing project alignment and knowledge sharing.

Personal impact: You gain a streamlined way to incorporate important email context into your work, saving time and improving output quality.

• Unified web and work chat experience with dedicated Work IQ button [Windows, Web]

Use a new Work IQ button located in the top left of the Chat UI to switch access to work data on/off without leaving the chat experience.

Details:

What changed: Web and work chats are now unified into a single chat interface that now has a dedicated Work IQ button to control access to work data. Previously, users switched between separate web and work chat tabs, increasing cognitive load and inconsistency. This change unifies the chat experience and simplifies how users control access to work data when using chat.

Why: Combining chats into one interface with a toggle reduces confusion and streamlines user workflows by providing quick control over access to work data.

Try this:

1. Open Microsoft 365 Copilot Chat.
2. Locate the Work IQ button in the top left of the Chat interface.
3. Work date is on by default; enable or disable work data access as needed by selecting the button.

Why this matters: A unified chat interface reduces switching and helps users focus on their tasks with clearer data context.

Business impact: Teams benefit from a consistent chat experience that improves productivity and reduces user errors.

Personal impact: You spend less time navigating tabs and more time interacting with relevant data.

Microsoft 365 Copilot app

• Page steering and auto-triggering of pages on mobile [Android, iOS]

Users can now steer, refine, and edit pages using Copilot commands like "Shorten this page." They can also prompt Copilot to auto-create pages from chat, such as "Create a new page for XYZ."

Details:

What changed: Copilot now supports page steering on mobile devices, allowing users to modify page content with natural language commands. Previously, users had to manually edit pages without AI assistance. Additionally, Copilot can auto-trigger new page creation from chat prompts, streamlining content generation.

Why: These changes simplify content management on mobile by reducing manual editing and speeding up page creation, improving user productivity and content accuracy.

Try this:

1. Open a page on your mobile device and say, "Shorten this page."
2. In chat, type "Create a new page for [topic]."
3. Review and edit the generated page content as needed.

Why this matters: This update reduces friction in mobile content editing and creation, enabling faster and more precise page management.

Business impact: Teams can produce and refine content more efficiently on mobile, supporting faster collaboration and information sharing.

Personal impact: You save time editing pages and can quickly generate new content without switching devices or apps.

• Simplified design for the Microsoft 365 Copilot app [Windows, Mac, Web]

A refreshed design for the Microsoft 365 Copilot web and desktop app simplifies the user experience to drive engagement with Copilot. This includes updates to the chat home screen, chat response layout, and navigation pane.

Roadmap ID: 561488

Details:

What changed: The Microsoft 365 Copilot app now features an updated chat home screen, a streamlined chat response layout, and a redesigned navigation pane. The new design helps users more easily navigate the app and stay focused across web and desktop platforms.

Why: Simplifying the app interface helps users engage more easily with Copilot, reducing the time needed to find features and improving overall usability.

Try this:

1. Open the Microsoft 365 Copilot app on web or desktop.
2. Explore the updated chat home screen to quickly access recent conversations.
3. Use the new navigation pane to switch between chats and tools more efficiently.

Why this matters: A clearer interface helps users interact with Copilot faster and more intuitively, increasing productivity.

Business impact: Teams experience smoother collaboration with fewer interruptions caused by navigation or layout confusion.

Personal impact: You spend less time navigating the app and more time focusing on your tasks.

• Generate and edit images in Copilot Cowork [Android, Windows, iOS, Mac, Web]

Create and modify images in Copilot Cowork using OpenAI's ChatGPT Images 2.0 model for enhanced visual content generation.

Details:

What changed: Copilot Cowork integrates OpenAI's ChatGPT Images 2.0 model to generate and edit image artifacts. Previously, image creation required external tools. This update enables in-app image generation and editing, streamlining creative workflows.

Why: Embedding image generation within Copilot Cowork reduces context switching and accelerates content creation.

Try this:

1. Open Copilot Cowork.
2. Enter a description to create an image using ChatGPT Images 2.0.
3. Use editing tools to refine the image within Cowork.

Why this matters: Integrated image generation enhances creativity and productivity by keeping visual content creation within the collaboration environment.

Business impact: Teams can produce visual assets in their workflow without relying on separate design software.

Personal impact: You save time by generating and editing images directly in your collaboration workspace.

Original source

Welcome to the August 2026 update. New this month for Copilot, chat history, chart/PivotTable skills, Python skill, as well as change history.

Excel for Windows, Mac, and web

• Copilot in Excel: change history skill
• #FIA
• Copilot in Excel: chat history
• #FIA
• Copilot in Excel: chart and PivotTable skills
• Copilot in Excel: Python skill (Insiders)

Excel for Windows, Mac, and web

Excel in Excel: change history skill #FIA

The change history skill helps users understand how a workbook has evolved over time. Copilot can summarize recent changes, identify who made edits, and explain how both people and AI have modified the workbook. It can also help undo specific edits or restore formulas by returning the workbook to a previous working state.

Copilot in Excel: chat history #FIA

Use the menu icon in the upper left corner of the Copilot in Excel pane to access your Copilot chat history. Conversations are listed based on recency, with your most recent chat at the top of the list. Select a conversation from the list to view it. Access to Copilot in Excel conversation history requires a Microsoft 365 Copilot commercial license.

Copilot in Excel: Chart and PivotTable skills

Turn complex data into clear, polished insights. Create and organize PivotTables to summarize your data with new-built in capabilities. Use @chart-design to improve visualizations.

Copilot in Excel: Python skill (Insiders)

Analyze and visualize complex data with Python in Excel. Create editable, refreshable Python formulas and uncover deeper insights directly in your workbook. Start using @ python-in-excel to insert Python into your workbook today.

Many of these features are the result of your feedback. THANK YOU! Your continued Feedback in Action (#FIA) helps improve Excel for everyone. Please let us know how you like a particular feature and what we can improve upon—"Give a compliment" or "Make a suggestion". You can also submit new ideas or vote for other ideas via Microsoft Feedback.

Subscribe to our Excel Blog and the Insiders Blog to get the latest updates. Stay connected with us and other Excel fans around the world – join our Excel Community and follow us on X, formerly Twitter.

Special thanks to our Excel MVPs David Benaim, Bill Jelen, Alan Murray, and John Michaloudis for their contribution to this month's What's New in Excel article. David publishes weekly YouTube videos and regular LinkedIn posts about the latest innovations in Excel and more. Bill is the founder and host of MrExcel.com and the author of several books about Excel. Alan is an Excel trainer, author and speaker, best known for his blog computergaga.com and YouTube channel with the same name. John is the Founder & Chief Inspirational Officer at MyExcelOnline.com where he passionately teaches thousands of professionals how to use Excel to stand out from the crowd.

Original source

What's Changed

• .NET: Add session-persisted chat client routing by westey (@westey-m) in #7641
• .NET: Fix snake_case argument names in Harness file tool descriptions by westey (@westey-m) with @Copilot in #7731
• .NET: Pass IServiceProvider to ChatClientAgent in AddAIAgent overloads by westey (@westey-m) in #7737
• .NET: Python: Clarify PR review comment resolution by Evan Mattson (@moonbox3) in #7746
• .NET: Update AG-UI samples for latest MAF + AG-UI SDK and align with docs by Daniel Roth (@danroth27) in #7295
• .NET: Migrate remaining Foundry hosted samples to source deployment by Roger Barreto (@rogerbarreto) in #7668
• .NET: agent-hooks interception contract as a first-class experimental feature by MohammadHaroonAbuomar in #7564
• .NET: Forward AG-UI context and additional properties by Javier Calvarro Nelson (@javiercn) in #7742
• .NET: Suppress Swagger UI CodeQL alert in AgentWebChat sample by SergeyMenshykh in #7764
• .NET: Remove AGUI history special cases from ChatClientAgent by Javier Calvarro Nelson (@javiercn) in #7741
• .NET: Fix A2A streaming artifact updates by SergeyMenshykh in #7722
• Python: Harness blog part4 samples by westey (@westey-m) in #7698
• .NET: Clarify compaction provider and chat reducer choices by Ravi Kiran Pagidi (@ravikiranpagidi) in #7678
• .NET: Add Azure Blob Storage session persistence by Korolev Dmitry (@DeagleGross) in #1893
• .NET: Persist hosted agent state in Foundry by Roger Barreto (@rogerbarreto) in #7649
• .NET: [BREAKING] Migrate MCP long-running task support to the 2026-07-28 Tasks extension by Peter Ibekwe (@peibekwe) in #7774
• .NET: Add feature-usage bitmask by Peter Ibekwe (@peibekwe) in #7709
• Bump Anthropic from 12.35.1 to 12.42.0 by Dependabot (@dependabot)[bot] in #7778
• .NET: Fix ReasoningSummary passthrough in GitHub Copilot resume config by Chandramouleswaran (@chandramouleswaran) in #6441
• .NET: Bump AgentMemory from 1.3.0 to 1.4.1 by Dependabot (@dependabot)[bot] in #7639
• .NET: Add support for Resilient long-running and Steerable Foundry Hosted Agents by Roger Barreto (@rogerbarreto) in #7370
• .NET: Update version for 1.19.0 release by Roger Barreto (@rogerbarreto) in #7814

New Contributors

• Daniel Roth (@danroth27) made their first contribution in #7295
• Manjunath Janardhan (@manjunathshiva) made their first contribution in #7755
• ALEX LILUZ (@alexliluz) made their first contribution in #7766
• Dan Fiedler (@danfiedler-msft) made their first contribution in #7768
• Ravi Kiran Pagidi (@ravikiranpagidi) made their first contribution in #7678
• Sadok Barbouche (@cr-sbarbouche) made their first contribution in #7734
• Ran Shemtov (@ranst91) made their first contribution in #7423
• Quim Muntal (@qmuntal) made their first contribution in #7754

Full Changelog: dotnet-1.18.0...dotnet-1.19.0

Original source