Connor PeetandGitHub
c7e690b5f5
* agentHost: adopt channel-based AHP wire model
Adopts the channel-based Agent Host Protocol revision from
microsoft/agent-host-protocol#127. Subscriptions, action delivery, and
protocol notifications now all route over named channels identified by a
top-level `channel: URI` field, replacing the pre-channels subscribe /
dispatch / notify model.
- Renames `ROOT_STATE_URI` from `agenthost:/root` to `ahp-root://` and
adds an `isAhpRootChannel` helper that tolerates both the canonical
wire form and the workbench `URI` round-tripped form (`ahp-root:`).
- Threads a `channel` parameter through every action dispatch path:
`IAgentService.dispatchAction`, `IAgentConnection.dispatch`,
`AgentHostStateManager.dispatchServerAction` / `dispatchClientAction`,
and `AgentSubscriptionManager.dispatchOptimistic`. Individual action
payloads no longer carry `session` / `terminal` / `changeset` fields;
the envelope carries the channel.
- Replaces the `{ method: 'notification', params: { notification } }`
wrapper with top-level JSON-RPC methods (`root/sessionAdded`,
`root/sessionRemoved`, `root/sessionSummaryChanged`, `auth/required`).
Each notification's params now carry their own `channel: URI` field.
- Renames the per-command identifying field to `channel` for the channel-
scoped commands (`createSession`, `disposeSession`, `createTerminal`,
`disposeTerminal`, `fetchTurns`, `completions`,
`invokeChangesetOperation`). Connection-level commands hard-code the
root channel string.
- Updates the subscribe result to `{ snapshot? }` and the
`SubscribeParams` / `UnsubscribeParams` field name from `resource` to
`channel`.
- Drops the removed `ProtocolNotification`, `NotificationType`,
`NotificationMethodParams`, and `NotificationMap` exports; provides a
thin compat `NotificationType` constant keyed by method name for
consumers that still discriminate notification variants.
- Adapts `AgentSubscription` routing to switch on `envelope.channel`
rather than inspecting per-action URI fields (`_isRelevantEnvelope`
replaces `_isRelevantAction`).
- Migrates all producers (`agentService`, `agentSideEffects`,
`agentConfigurationService`, `agentHostChangesetService`,
`agentHostTerminalManager`, `agentHostStateManager`,
`protocolServerHandler`, Claude/Copilot agent sessions, terminal
manager, etc.) and consumers (workbench session handler, terminal
contribution, pty, customization harness, provider tests) to the new
shapes.
(Commit message generated by Copilot)
* agentHost: address Copilot review for channels migration
Addresses feedback from Copilot's review of #317251:
- Update real-SDK integration test helpers and protocol integration
tests to use the channel-based command shapes (rename `session` /
`resource` to `channel`, add `channel: 'ahp-root://'` to
connection-level commands, drop `session` from action payloads, route
via params-level `channel`).
- Treat the canonical `ahp-root://` and the URI-normalized `ahp-root:`
forms as equivalent in `_isRelevantToClient` so root broadcasts reach
a client that subscribed using either form (mirrors `isAhpRootChannel`
already in use elsewhere).
- Drop a `..` hop from the `NotificationType` import path in the local
and remote session-provider tests; import from
`state/sessionActions.js` directly.
- Drop a stale post-merge `session: SESSION_STR` in
`claudeMapSessionEvents.test.ts:Test 9.5` and the matching
`requestResourceAccess` test expectation in
`agentHostFileSystemProvider.test.ts` so they match the new
channel-based shapes (root cause of the macOS browser CI failure).
(Commit message generated by Copilot)
* tests
* import
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 and 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.