ad6a5fe3be
* nes: fix: share in-flight speculative requests across concurrent calls A speculative request is fired when a suggestion is shown, betting on the document state that results if the user accepts it. `consumePending()` nulled the pending slot as soon as the first `getNextEdit` caller claimed the request, so a second overlapping caller for the same post-edit state could not discover it and issued a duplicate model request — losing the latency win, the `ReusedRequestKind.Speculative` telemetry, and the `liveDependentants` sharing that keeps a joined request alive for multiple dependants. Rename it to `claimPending()` and keep claimed requests in a map until their `result` settles, so concurrent callers join the in-flight request instead. A map rather than a single slot: several speculatives can be claimed at once (e.g. one per document), and evicting one on the arrival of another would reintroduce the same bug. Claimed requests deliberately survive the "nobody will want this anymore" cancellation reasons (Replaced, Superseded, Rejected, IgnoredDismissed, trajectory divergence) since they have a live consumer; `invalidateClaimed()` still cancels them for reasons that invalidate the result itself (CacheCleared, DocumentClosed, Disposed). Also settle `firstEdit`/`result` in `_runSpeculativeProviderCall`'s outer catch. Previously a throw at the first `editStream.next()` left them unsettled forever, hanging any caller that reused the request — a pre-existing bug that the claimed map would otherwise widen into a permanent map entry. Behavior is unchanged when `inlineEdits.speculativeRequests` is off: the claimed map can only be populated via `_triggerSpeculativeRequest`, which is gated on the setting, so every new lookup degenerates to an empty-map no-op. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: b9cc340f-f2af-491d-a411-6e1c2c19583e * nes: test: cover speculative that throws before its first streamed edit The outer catch in `_runSpeculativeProviderCall` settles `firstEdit`/`result` so a caller reusing the request cannot hang, but nothing exercised it: every existing speculative test yields at least one edit or is cancelled. Add a `throwBeforeFirstYield` harness behavior and a regression test that claims such a speculative. `getNextEdit` rethrows the underlying error for `NoNextEditReason.Unexpected`, so the joiner rejects with the provider error instead of awaiting forever, and the released claim lets the following request recover with a fresh provider call. Verified to fail without the fix: the joining call times out after 8s. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: b9cc340f-f2af-491d-a411-6e1c2c19583e --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: b9cc340f-f2af-491d-a411-6e1c2c19583e
GitHub Copilot - Your autonomous AI peer programmer
GitHub Copilot is an AI peer programming tool that transforms how you write code in Visual Studio Code.
GitHub Copilot agents handle complete coding tasks end-to-end, autonomously planning work, editing files, running commands, and self-correcting when they hit errors. You can also leverage inline suggestions for quick coding assistance and inline chat for precise, focused edits directly in the editor.
Sign up for GitHub Copilot Free!
Getting access to GitHub Copilot
Sign up for GitHub Copilot Free, or request access from your enterprise admin.
To access GitHub Copilot, an active GitHub Copilot subscription is required. You can read more about our business and individual offerings at github.com/features/copilot.
Build with autonomous agents
Let AI agents implement complex features end-to-end. Give an agent a high-level task and it breaks the work into steps, edits multiple files, runs terminal commands, and self-corrects when it hits errors or failing tests. Agents excel at building new features, debugging and fixing failing tests, refactoring codebases, and collaborating via pull requests.
Manage sessions from a central view. Run multiple agent sessions in parallel and track them in one place. Monitor session status, switch between active work, review file changes, and resume where you left off.
Run agents with your preferred harness. Use agents locally in VS Code, in the background via Copilot CLI, or Cloud via Copilot Coding Agent. You can also work with providers like Claude and Codex, and hand tasks off between agent types with context preserved all within the VS Code.
Use agents to plan before you build with the Plan agent, which breaks tasks into structured implementation plans and asks clarifying questions. When your plan is ready, hand it off to an implementation agent to execute it. You can also delegate tasks to cloud agents that create branches, implement changes, and open pull requests for your team to review.
More ways to code with AI
Receive intelligent inline suggestions as you type with ghost text suggestions and next edit suggestions, helping you write code faster. Copilot predicts your next logical change, and you can accept suggestions with the Tab key.
Use inline chat for targeted edits by pressing Ctrl+I/Cmd+I to open a chat prompt directly in the editor. Describe a change and Copilot suggests edits in place for refactoring methods, adding error handling, or explaining complex algorithms without leaving your editor.
Customize AI for your workflow
Agents work best when they understand your project's conventions and have the right tools. Tailor Copilot so it generates code that fits your codebase from the start.
Project context. Use custom instructions to specify project-wide or task-specific context and coding guidelines.
Add specialized capabilities. Teach Copilot specialized capabilities with agent skills or define specialized personas with custom agents.
Connect to external tools and services. Extend agents further with tools from MCP servers and extensions to give Copilot a gateway to external data sources, APIs, or specialized tools.
Supported languages and frameworks
GitHub Copilot works on any language, including Java, PHP, Python, JavaScript, Ruby, Go, C#, or C++. Because it’s been trained on languages in public repositories, it works for most popular languages, libraries and frameworks.
Version compatibility
As Copilot Chat releases in lockstep with VS Code due to its deep UI integration, every new version of Copilot Chat is only compatible with the latest and newest release of VS Code. This means that if you are using an older version of VS Code, you will not be able to use the latest Copilot Chat.
Only the latest Copilot Chat versions will use the latest models provided by the Copilot service, as even minor model upgrades require prompt changes and fixes in the extension.
Privacy and preview terms
By using Copilot Chat you agree to GitHub Copilot chat preview terms. Review the transparency note to understand about usage, limitations and ways to improve Copilot Chat during the technical preview.
Please refer to our Privacy Statement to learn about the data we collect, how we use it, and the controls available to you.
To get the latest security fixes, please use the latest version of the Copilot extension and VS Code.
Resources & next steps
- Sign up for GitHub Copilot Free: Explore Copilot's AI capabilities at no cost before upgrading to a paid plan.
- If you're using Copilot for your business, check out Copilot Business and Copilot Enterprise.
- Copilot Quickstart: Discover the key features of Copilot in VS Code.
- Agents Tutorial: Get started with autonomous agents across different environments.
- VS Code on YouTube: Watch the latest demos and updates on the VS Code channel.
- Frequently Asked Questions: Get answers to commonly asked questions about Copilot in VS Code.
- Provide Feedback: Send us your feedback and feature request to help us make GitHub Copilot better!
Data and telemetry
The GitHub Copilot Extension for Visual Studio Code collects usage data and sends it to Microsoft to help improve our products and services. Read our privacy statement to learn more. This extension respects the telemetry.telemetryLevel setting which you can learn more about at https://code.visualstudio.com/docs/supporting/faq#_how-to-disable-telemetry-reporting.
Trademarks
This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.
License
Copyright (c) Microsoft Corporation. All rights reserved.
Licensed under the MIT license.