VS Code GitHub Copilot Telemetry Configuration Explained

GitHub Copilot in VS Code sends telemetry data to Microsoft by default. This data includes usage patterns, error reports, and performance metrics. Many developers want to control what data leaves their machine for privacy or compliance reasons. This article explains the telemetry settings available in VS Code for GitHub Copilot. You will learn how to view, modify, and disable telemetry collection at the editor level and the extension level.

What Telemetry Data Does GitHub Copilot Collect?

GitHub Copilot in VS Code collects telemetry data to improve the AI model and the extension itself. The data includes:

Usage Metrics

The extension logs how often you accept, dismiss, or manually open suggestions. It also records which files and languages you use Copilot with. This data helps Microsoft understand which scenarios Copilot handles well and where it needs improvement.

Error and Performance Data

When Copilot fails to load a suggestion or returns an error, the extension sends error logs. Performance data includes response times and whether the suggestion was generated locally or from the cloud. This data does not include your source code.

Aggregate Interaction Data

Copilot tracks interactions like the number of completions shown per minute, the length of accepted completions, and the time between keystrokes. This data is aggregated and does not identify individual users. It is used to measure system health and model accuracy.

How to View Current Telemetry Settings in VS Code

Before changing any settings, you should check what telemetry level is currently active. Follow these steps to view the current configuration.

1. Open VS Code Settings
   Press Ctrl + Comma on Windows or Cmd + Comma on macOS. Alternatively, go to File > Preferences > Settings.
2. Search for “telemetry”
   Type telemetry in the search bar at the top of the Settings window. The results show all telemetry-related settings.
3. Locate the Telemetry Level setting
   Find the setting labeled Telemetry: Telemetry Level with the ID telemetry.telemetryLevel. The current value is displayed in the dropdown.
4. Check the Copilot-specific telemetry setting
   In the same search results, look for GitHub Copilot Advanced: Telemetry Opt Out with the ID github.copilot.advanced.telemetry.optOut. If the checkbox is checked, Copilot telemetry is disabled.

How to Disable Telemetry for GitHub Copilot

You have two independent controls for telemetry. The global VS Code telemetry level affects all extensions, including Copilot. The Copilot-specific setting only affects the Copilot extension. You can use either or both.

Method 1: Disable All VS Code Telemetry

1. Open Settings
   Press Ctrl + Comma (Windows) or Cmd + Comma (macOS).
2. Search for telemetry.telemetryLevel
   Type telemetry.telemetryLevel in the search bar.
3. Set the value to “off”
   Click the dropdown and select off. This disables all telemetry from VS Code and all extensions, including Copilot.

Method 2: Disable Only Copilot Telemetry

1. Open Settings
   Press Ctrl + Comma (Windows) or Cmd + Comma (macOS).
2. Search for github.copilot.advanced.telemetry.optOut
   Type github.copilot.advanced.telemetry.optOut in the search bar.
3. Check the checkbox
   Click the checkbox to set it to true. This disables telemetry for the Copilot extension only. Other VS Code telemetry continues to send data.

Method 3: Use settings.json

1. Open settings.json
   Press Ctrl + Shift + P (Windows) or Cmd + Shift + P (macOS) to open the Command Palette. Type Preferences: Open Settings (JSON) and select it.
2. Add the telemetry settings
   Insert the following lines inside the JSON object:
   "telemetry.telemetryLevel": "off",
"github.copilot.advanced.telemetry.optOut": true
3. Save the file
   Press Ctrl + S (Windows) or Cmd + S (macOS). The settings take effect immediately.

Common Misconceptions and Limitations

Disabling Telemetry Disables Copilot Features

Disabling telemetry does not stop Copilot from generating code suggestions. The extension still works fully. Telemetry only affects data sent to Microsoft for analysis. Your use of the AI assistant remains unaffected.

Telemetry Settings Are Per-User

Telemetry settings in VS Code are stored in the user settings file. They apply to all workspaces opened with that user profile. If you share a machine, each user must configure their own settings. Workspace-level settings do not override user telemetry settings.

Crash Reporter Is Separate

The crash reporter setting telemetry.enableCrashReporter controls only crash dumps. Setting it to false does not stop usage telemetry. To stop all data collection, you must set telemetry.telemetryLevel to “off” or use the Copilot-specific opt-out.

Telemetry Data May Still Be Collected by GitHub

Disabling telemetry in VS Code stops the extension from sending data. However, GitHub may still collect data through the Copilot API or the GitHub website. This article covers only VS Code-side telemetry. For GitHub-level telemetry, review your GitHub account settings.

VS Code Telemetry Levels vs Copilot Opt-Out: Key Differences

Item	VS Code Telemetry Level (telemetry.telemetryLevel)	Copilot Opt-Out (github.copilot.advanced.telemetry.optOut)
Scope	All VS Code extensions and the editor itself	Only the GitHub Copilot extension
Default value	“all” (sends all telemetry)	false (telemetry is on)
Effect on Copilot	Stops all Copilot telemetry when set to “off”	Stops only Copilot telemetry; other extensions continue sending
Configuration method	Settings UI dropdown or settings.json	Settings UI checkbox or settings.json
Requires restart	No, changes apply immediately	No, changes apply immediately

You can now configure telemetry for GitHub Copilot in VS Code to match your privacy needs. Use the global telemetry level to disable all data collection or the Copilot-specific opt-out to target only Copilot. After changing settings, verify them by reopening the Settings page and checking the displayed values. For enterprise environments, consider deploying these settings via a group policy or a shared settings.json file to ensure compliance across all developers.