Rob Lourens
9cd698c36b
* Sync built-in skills + add skill buttons for agent-host sessions Brings back the UX from #311815 for the Agents window: - Sync built-in prompts (e.g. /merge, /create-pr) into the local agent-host customization bundle so agent-host sessions can run the same slash commands as the Copilot CLI extension. The enumeration helper now reads the BUILTIN_STORAGE bucket from IPromptsService and includes those entries in the bundle pushed to the harness, alongside workspace, user, and extension prompts. - Add four skill buttons to the changes view of agent-host sessions: Merge Changes, Create Pull Request, Create Draft Pull Request, and Sync Pull Request. Each button dispatches the matching slash command to the active session via IChatService, scoped to git + GitHub state context keys so the right buttons appear at the right time. The first registered button is hoisted as the primary blue toolbar button; the rest live in the apply submenu. - Suppress the duplicate Copilot CLI extension buttons (Commit, Sync, Create PR, etc.) when the active session is an agent-host session, clause in extensions/copilot/package.json. The check only narrows the chatSessionType==copilotcli rows; claude-code rows are unchanged. - Mark the agent-host chat contribution supportsPromptAttachments so /create-pr and friends parse as slash commands in the chat input. Tests: - agentHostSkillButtons.test.ts: action registration, context key reactivity, when-clause coverage. - enumerateLocalCustomizationsForHarness.test.ts: built-in skill enumeration is folded into the bundle with BUILTIN_STORAGE. - resolveCustomizationRefs.test.ts: built-in entries are resolvable through the existing ref resolution path. End-to-end verified manually: clicking 'Merge Changes' on a debug-test agent-host session dispatches '/merge', the agent host receives the slash command, expands the merge skill, and runs its tool steps. Copilot CLI extension buttons are not visible on agent-host sessions. (Written by Copilot) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * agent-host: read git.branchProtection in repo scope The git.branchProtection setting is resource-scoped, so its value can differ per workspace folder. Reading it without an override picked up the host window's active workspace value instead of the session's own repository value, which made the agent host show a Merge Changes button for sessions whose repo had a protected main branch. Pass the session's project URI as the resource override so we read the setting in the scope of that folder. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * agent-host: register skill buttons from sessions main, drop stale comment Move the skillButtons import to sessions.desktop.main.ts and sessions.web.main.ts so it is wired in both desktop and web sessions windows, instead of from the local-only contribution. Drop the now-redundant comment on supportsPromptAttachments in the chat session contribution registration. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * agent-host: register client filesystem provider for local in-process agent host Previously, `vscode-agent-client://` was only registered for WebSocket agent host transports (dynamic and env-var driven). The local in-process utility-process agent host had no provider, so plugin syncs from the renderer (used by `/create-pr`, `/merge` and other built-in skills) failed with `ENOPRO`. This wires the same reverse-RPC pattern over the existing MessagePort IPC: * Renderer registers an `AgentHostClientResourceChannel` (server channel) on its `MessagePortClient`, wrapping the renderer's `IFileService`. * The renderer's clientId is now used as the IPC ctx so the agent host can route reverse calls to a specific client. * Agent host hoists `AgentHostClientFileSystemProvider` to a single shared instance and, for utility-process IPC connections, registers an authority per connection backed by the new channel. Result: `vscode-agent-client://` URIs resolve identically for local and remote agent hosts, the in-memory `vscode-synced-customization://` bundle is reachable from the agent-host process, and built-in skills sync. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * agent-host: address Copilot review comments and fix branchProtection resource scope - resourceList now throws when target URI is not a directory - wrap BUILTIN_STORAGE listPromptFilesForStorage in try/catch so regular workbench prompts service (which throws on unknown storage) is handled - update test to model the throw case for regression coverage - use workingDirectory ?? project.uri as resource for git.branchProtection config lookup so worktree paths resolve the per-folder setting correctly (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, 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 additional 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.