2d2f4ae7b6
* Cover annotations, protocol contracts, and terminal lifecycle in agent host E2E Adds conformance coverage for protocol areas that no E2E test reached, chosen from the protocol-surface `uncovered` lists rather than to hit a number. - `suites/annotationsSuite.ts` — the whole `annotations/*` channel, which was covered by neither the E2E suite nor the frozen protocol suite. - `suites/protocolContractsSuite.ts` — liveness (`ping`), turn-history paging (`fetchTurns` / `chat/turnsLoaded`), connection recovery (`reconnect`, both the replay-gap and unresumable-subscription cases), and the rejection contract for the four declared-but-unsupported working-directory actions. - `stateOperationsSuite.ts` — terminal clear and exit, root's view of terminals appearing and disappearing, and queued-message promotion. `reconnect` is only answerable on a transport that has not completed the handshake, so it needs a second connection that can be dropped and re-established. `IAgentHostE2ETestContext.connectClient` is that seam; the shared per-test client cannot express it. The queued-message test started out asserting that two queued messages accumulate. They do not: a message queued onto an idle chat is promoted straight into a turn, so the queue is empty again by the next reduction. The dispatch envelope looked entirely normal, and every other test in that suite asserts only the result of its last dispatch, which is why this had gone unnoticed. The test now asserts the real contract, and KNOWN_ISSUES records the test-shape lesson. Protocol surface: commands 27/29 -> 28/29, actions 54/85 -> 59/85. The one remaining uncovered command and the eight `changeset/*` actions are covered by the changeset branch. Conformance tier 62 -> 73 tests; full suite 172 passing, 0 failing, stable across repeated runs. (Written by Copilot) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Drive the two new host-local turns with /rename instead of a bang command Windows CI timed out on `fetchTurns reports the turns a chat already has` and `a message queued on an idle chat is promoted straight into a turn`. Both needed a real turn that never reaches the model, and both used `!echo` to get one. That is a documented Windows defect, already recorded in KNOWN_ISSUES and already the reason `a bang command runs locally and exposes terminal output` is Windows-scoped: a successful bang command produces output but does not complete reliably, so waiting on `chat/turnComplete` hangs. `/rename` is handled by the same local-command dispatcher but spawns no shell, and it is exercised on Windows today by the host-features suite. Neither test cares how the turn was produced, only that one exists, so this removes the dependency rather than scoping the tests to non-Windows. (Written by Copilot) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Tighten notification predicates and correct the migration backlog table Addresses code review feedback: - The turn waits in the queued-message test and in `fetchTurns` now constrain `channel`, so a shared client cannot match a notification from another session's chat. - `dispatchAndWaitOnShared` now matches the action type as well as the channel and originating `clientSeq`. - The migration backlog table's third column listed symbols as uncovered that this change covers. Renamed it to "Protocol symbols", marked each row's actual status, and pointed at `coverage/protocol-surface.json` as the authoritative source. (Written by Copilot) 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 the Visual Studio Code 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 them 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 codebase, 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.