Why This Matters

Defaults are not always right for your context. A 5-minute settings pass now prevents weeks of annoyance and accidental privacy exposure later.

Concept Explained

Copilot settings live in three layers: editor-level (VS Code Settings → search 'Copilot'), account-level (github.com/settings/copilot), and org-level (for Business/Enterprise). Each layer overrides the one below. Editor settings control UX; account settings control privacy and training; org settings enforce policy.

How It Works

Editor settings are stored in settings.json and sync across your VS Code instances via Settings Sync. Account-level settings persist on GitHub's side. Org policies are pushed by admins and visible but not editable. When a setting conflicts, the most restrictive applies for privacy, the most specific for UX.

Step-by-Step Tutorial

1. Open Copilot settings

2. Configure ghost-text timing

3. Set the duplication filter

4. Toggle telemetry

5. Save a snapshot

Real-World Example

A junior dev at a startup left the training-data opt-out on its default (enabled). Three weeks later their code snippets — including an internal API key naming convention — had contributed to model training. A 30-second settings pass would have prevented it.

Example Prompts / Commands / Code

{
  "github.copilot.advanced": {
    "length": 500,
    "listCount": 3,
    "debug.overrideCAPIProxy": false
  },
  "github.copilot.editor.enableAutoCompletions": true,
  "github.copilot.editor.enableAutoTrigger": true,
  "editor.quickSuggestionsDelay": 400,
  "github.copilot.duplication": "block"
}

Common Mistakes

• Leaving duplication on 'Allow' for work code — risks importing GPL snippets.
• Disabling telemetry but forgetting the separate training-data opt-out.
• Setting the delay too low (<200ms) — Copilot interrupts typing rhythm.
• Not re-checking settings after extension updates — defaults change.

Best Practices

• Block public-code duplication for any code that will ship commercially.
• Disable training-data use for any work account.
• Save a settings snapshot every quarter.
• Use org-level policy when available — it can't be accidentally unset.

Troubleshooting

Practical Exercise

Frequently Asked Questions

Further Reading

• Copilot settings reference

Official References

• Configuring Copilot settings

Related lessons: BE-04, BE-34