How to Use GitHub Copilot With VS Code Profiles for Different Projects

Official documentation checked October 14, 2026.

VS Code profiles let you switch editor settings, extensions and shortcuts between workflows. You can use one profile for Python analysis and another for JavaScript development, while keeping project-specific instructions in the repository. Profiles organize configuration; they do not create isolated operating-system accounts or prevent AI from accessing sensitive files.

How Profiles Work with GitHub Copilot

A profile can contain its own user settings, extensions and other customizations. When creating one, you can copy selected configuration from another profile, use a template, or start empty. Some categories can instead use the Default Profile’s configuration. VS Code remembers profile associations for workspaces. See profile creation and configuration.

Installing Copilot in Default does not guarantee availability in every profile. Check the Extensions content for the selected profile. Apply Extension to all Profiles is an explicit action if you want that behavior; keep it profile-specific when you do not.

Profile user settings also do not override every workspace, language or managed setting. Inspect the effective setting in the actual project. Copilot’s current language map is github.copilot.enable, while chat.disableAIFeatures disables and hides AI features. Consult the setting-scope guide and AI settings reference.

Create a Profile for a Useful Project Workflow

1. Preserve the current setup. Save work and note the profile currently associated with the project. Decide which settings or extensions should differ. One profile per project is optional; several projects can share a workflow profile.
2. Open the Profiles editor. Use the Manage gear’s Profiles entry or the File > Preferences > Profiles menu where available. Select New Profile, choose a descriptive name, and inspect what will be copied or shared from Default before creating it.
3. Choose extensions deliberately. Include the required GitHub-published Copilot components and relevant language tools. An Empty Profile starts without your custom extensions, so verify installation and enablement there. Do not assume an icon’s appearance proves all setup succeeded.
4. Configure the intended language behavior. In Settings, inspect github.copilot.enable and change only the intended entries. For example, retain a deliberate Markdown restriction while allowing Python suggestions. Use Apply Setting to all Profiles only when you want a setting shared across workflows.
5. Associate and test. Use the profile for the current project window, open a small non-sensitive source file, and inspect the account/status message. Test a visible inline suggestion and a bounded Chat request separately. Record the result before changing another setting.

If the project needs shared coding guidance, review an existing .github/copilot-instructions.md before adding instructions. Use concise Markdown about the real language version, naming conventions and tests; this file does not require the scoped-instruction YAML header. Keep credentials out of it. VS Code’s custom-instruction guide distinguishes always-on and scoped files.

Custom instructions apply to supported Chat/agent requests and are not taken into account for inline ghost-text suggestions as you type, according to the current VS Code guide. A profile enabling completions therefore does not make repository instructions an enforced rule for every suggestion. Use formatters, linters and tests when a convention must be checked.

Switch Between Profiles and Confirm the Effective Setup

Save work, open the Command Palette and run Profiles: Switch Profile, then select the intended profile. You can also use Use this Profile for Current Window in the Profiles editor. Inspect the selected profile and workspace association before testing Copilot.

For an explicit launch, the documented CLI supports a project path and profile name:

code /path/to/project --profile "Web Development"

Replace the placeholder with your actual project path. If that profile name does not exist, VS Code creates a new empty profile, so check spelling before interpreting missing extensions as a Copilot failure. A profile switch does not change the repository branch or independently authorize another GitHub account.

Common Mistakes When Using Copilot with Profiles

Settings unexpectedly affect other profiles: inspect shared Default categories and Apply Setting to all Profiles. Compare the actual User, Workspace, folder and language scopes. Change the unintended value rather than recreating or deleting the profile.

Copilot is missing: inspect the active profile’s extensions and account state. Check whether it was copied, explicitly applied to all profiles, or omitted from an Empty Profile. Avoid unverified “Enable (Profile)” instructions or assuming a reinstall will fix an account/policy error.

Repository instructions appear ignored: confirm the file’s supported location and scope, the session and selected agent, and whether the feature uses custom instructions. Verify the output rather than assuming a file enforces behavior. Do not misdiagnose inline suggestions using a Chat-only instruction setting.

Backup or sync behaves differently: use the profile’s Export… action for a checked local .code-profile backup, and inspect what it includes before sharing. Use the import action in the Profiles editor when restoration is needed. Settings Sync has its own category and size/count limits, so inspect the specific sync error instead of assuming a universal local-profile cap. See Settings Sync. Do not clear all cloud data to repair one profile.

Profile Settings and Project Instructions: Different Scopes

Keep profiles small enough to understand, test the same project after switching, and share only reviewed configuration. This reduces repetitive setup while keeping the source of each effective Copilot setting clear.