-
Notifications
You must be signed in to change notification settings - Fork 7
docs: improve README #2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
webbrain-one
wants to merge
1
commit into
yulin0629:main
Choose a base branch
from
webbrain-one:webbrain/readme-improvement
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
Repository: yulin0629/github-copilot-tutorial
Length of output: 4741
🌐 Web query:
Visual Studio Marketplace GitHub Copilot Chat GitHub.copilot current listing companion extension installed with GitHub Copilot💡 Result:
As of August 2026, the installation and management of GitHub Copilot features have been unified, and the previously separate "GitHub Copilot Chat" extension is no longer a distinct, manually installed companion extension in modern development environments [1][2]. In Visual Studio 2022 (version 17.10 and later), GitHub Copilot and GitHub Copilot Chat are integrated into a single, built-in extension [3][1]. This unified experience is included by default with all Visual Studio workloads and is managed directly through the Visual Studio Installer rather than the Marketplace [1][2]. For older versions of Visual Studio (17.8 and 17.9), these features were provided as two separate extensions, but this model has been deprecated in favor of the integrated, unified package [1][2]. Similarly, in Visual Studio Code, the evolution of the Copilot extensions has led to their consolidation. The GitHub Copilot Chat repository was archived in May 2026 [4], and its functionality has been integrated into the core GitHub Copilot experience in VS Code [5][6]. Consequently, users no longer need to install a separate "companion" extension to access chat features; installing the primary GitHub Copilot extension provides the complete suite of AI-assisted capabilities [5].
Citations:
🏁 Script executed:
Repository: yulin0629/github-copilot-tutorial
Length of output: 32207
🌐 Web query:
site:code.visualstudio.com GitHub Copilot Chat extension bundled integrated GitHub Copilot VS Code 2026💡 Result:
As of August 13, 2026, GitHub Copilot Chat is no longer a separate, manually installed extension in Visual Studio Code [1]. Over the course of 2025 and early 2026, Visual Studio Code underwent a transition to consolidate all Copilot functionality [2][3]. Previously, Copilot features were split between two extensions: the original GitHub Copilot extension (for ghost text/inline suggestions) and the GitHub Copilot Chat extension [2]. Key milestones in this transition included: - Deprecation of the original GitHub Copilot extension: By early 2026, the original GitHub Copilot extension was deprecated and automatically uninstalled when users updated VS Code, with all its functionality migrated to the Copilot Chat extension [2][3]. - Integration into VS Code: By the release of version 1.116, GitHub Copilot became a built-in feature of Visual Studio Code [1]. New users no longer need to install any extension to access Copilot capabilities, such as chat, inline suggestions, and agents [1]. These AI features are available out of the box with a standard VS Code installation, requiring only a GitHub account sign-in to enable them [1][4]. Existing users who already had the extensions installed were not negatively affected by these changes, as the system managed the transition automatically [1]. If you wish to disable these built-in AI features, you can still do so via the chat.disableAIFeatures setting [1].
Citations:
🌐 Web query:
site:marketplace.visualstudio.com/items?itemName=GitHub.copilot-chat "companion extension"💡 Result:
In software development, particularly within environments like Visual Studio Code, a companion extension is a secondary tool designed to work in conjunction with another primary application, extension, or service to extend its functionality, bridge environments, or improve workflow integration [1][2][3]. Key characteristics and roles of companion extensions include: Environmental Bridging: They are often used to facilitate communication between different environments, such as a local host machine and a remote development environment (e.g., a dev container, SSH, or WSL session) [2]. A companion extension may handle tasks like certificate management or synchronization across these boundaries that the primary extension cannot manage alone [2]. Feature Enhancement: Some companion extensions provide additional features to a primary tool, such as AI-powered assistance, specialized visualization (like LaTeX rendering), or specific workflow integrations (e.g., file switching or testing tools) that are kept separate from the core codebase [1][4][5][3]. Workflow Integration: They may enable seamless interaction between external tools (like a CLI or browser-based service) and the code editor [1][6]. For example, a companion extension might allow a CLI tool to access editor context (such as open files or selected text) or enable browser-based task submission for competitive programming directly from the IDE [1][6]. Compatibility: Companion extensions are typically dependent on the primary tool they support; they are often installed specifically to augment that primary product [1][2][3]. They are generally not standalone applications and provide little value without the host software they are designed to accompany [2][3].
Citations:
🏁 Script executed:
Repository: yulin0629/github-copilot-tutorial
Length of output: 1105
🏁 Script executed:
Repository: yulin0629/github-copilot-tutorial
Length of output: 9668
Update the installation instructions for current VS Code.
VS Code 1.116 and later has GitHub Copilot built in. Users only need to sign in to enable Copilot Chat. The Marketplace listing still describes the older two-extension model, so do not state that Chat is integrated into, or always installed with, GitHub Copilot. Make the instructions version-specific.
🤖 Prompt for AI Agents
Source: MCP tools