3eb10e18b3
* chat: flush queued/steering messages when a streamed session turn completes Contributed chat sessions whose in-progress turn is streamed via activeResponseCallback (progressObs) — e.g. Copilot cloud sessions — register a synthetic pending request while streaming. A message sent mid-turn is therefore queued as a steering/queued message. The streaming-completion branch in loadRemoteSession deleted that pending request without flushing the queue, so the queued message was stranded in the model forever and never sent (steering 'limbo'). Mirror the normal request-completion path by calling processPendingRequests when the streamed turn completes. It is a no-op while another request is in flight and returns early for server-managed (agent-host) queues, so it is safe on every completion tick. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * chat: true mid-turn steering for cloud sessions Builds on the queued-message flush fix to inject a steer into a live cloud turn instead of only sending it after the turn settles, matching github.com/copilot/agents. Core (chatServiceImpl): for non-server-managed streamed (activeResponseCallback) sessions, dispatch a queued Steering message immediately when the in-flight pending request is the synthetic streamed-turn tracker (no requestId) — never over a real in-flight request. Re-establish tracking on the next progress tick so the turn stays in-progress. Extension (copilotCloudSessionsProvider): - Track live TaskTurnStreamer taskIds; when a stream is already active, handleTaskFollowUp only POSTs /steer and lets the running stream render the injected result (no second streamer). - Make the follow-up stream yield-aware (mirrors the Copilot CLI provider): poll context.yieldRequested and return on yield so the chat service flushes the next steer immediately. - Choose the render mode from the pre-steer task state: a steer into an active turn renders mode:'current' (the injection has no new task.sessions[] row, so mode:'next' would time out); a steer onto a settled task renders mode:'next'. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * chat: address review — fix synthetic-tracker race, tracking restore, stale task state - Identify the synthetic streamed-turn pending request via an explicit WeakSet instead of `requestId === undefined`: real requests are inserted into _pendingRequests before their requestId is assigned, so the old guard could delete a live request and start a concurrent invocation. - Restore in-progress tracking deterministically when the immediate-steer dispatch settles (hook responseCompletePromise) instead of relying on a future progress tick that may never fire. - Cloud provider: treat a follow-up as mid-turn (render mode:'current') only when BOTH the task and its latest turn are active, so a terminal task with a stale in_progress latest turn doesn't pick a streamer that exits before the steered turn appears. - Rework the regression tests: the steering test now asserts immediate dispatch, no duplicate dispatch on completion, and preserved in-progress tracking; a separate test covers completion-flush of a non-steering queued message. - Condense multi-line inline comments. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Visual Studio Code - Open Source ("Code - OSS")
The Repository
This repository ("Code - OSS") is where we (Microsoft) develop the Visual Studio Code product together with the community. Not only do we work on code and issues here, but we also publish our roadmap, monthly iteration plans, and our endgame plans. This source code is available to everyone under the standard MIT license.
Visual Studio Code
Visual Studio Code is a distribution of the Code - OSS repository with Microsoft-specific customizations released under a traditional Microsoft product license.
Visual Studio Code combines the simplicity of a code editor with what developers need for their core edit-build-debug cycle. It provides comprehensive code editing, navigation, and understanding support along with lightweight debugging, a rich extensibility model, and lightweight integration with existing tools.
Visual Studio Code is updated monthly with new features and bug fixes. You can download it for Windows, macOS, and Linux on Visual Studio Code's website. To get the latest releases every day, install the Insiders build.
Contributing
There are many ways in which you can participate in this project, for example:
- Submit bugs and feature requests, and help us verify as they are checked in
- Review source code changes
- Review the documentation and make pull requests for anything from typos to new content.
If you are interested in fixing issues and contributing directly to the code base, please see the document How to Contribute, which covers the following:
- How to build and run from source
- The development workflow, including debugging and running tests
- Coding guidelines
- Submitting pull requests
- Finding an issue to work on
- Contributing to translations
Feedback
- Ask a question on Stack Overflow
- Request a new feature
- Upvote popular feature requests
- File an issue
- Connect with the extension author community on GitHub Discussions or Slack
- Follow @code and let us know what you think!
See our wiki for a description of each of these channels and information on some other available community-driven channels.
Related Projects
Many of the core components and extensions to VS Code live in their own repositories on GitHub. For example, the node debug adapter and the mono debug adapter repositories are separate from each other. For a complete list, please visit the Related Projects page on our wiki.
Bundled Extensions
VS Code includes a set of built-in extensions located in the extensions folder, including grammars and snippets for many languages. Extensions that provide rich language support (inline suggestions, Go to Definition) for a language have the suffix language-features. For example, the json extension provides coloring for JSON and the json-language-features extension provides rich language support for JSON.
Development Container
This repository includes a Visual Studio Code Dev Containers / GitHub Codespaces development container.
-
For Dev Containers, use the Dev Containers: Clone Repository in Container Volume... command which creates a Docker volume for better disk I/O on macOS and Windows.
- If you already have VS Code and Docker installed, you can also click here to get started. This will cause VS Code to automatically install the Dev Containers extension if needed, clone the source code into a container volume, and spin up a dev container for use.
-
For Codespaces, install the GitHub Codespaces extension in VS Code, and use the Codespaces: Create New Codespace command.
Docker / the Codespace should have at least 4 cores and 6 GB of RAM (8 GB recommended) to run a full build. See the development container README for more information.
Code of Conduct
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
License
Copyright (c) Microsoft Corporation. All rights reserved.
Licensed under the MIT license.