Content exclusion: what it protects and what still leaks
Verdict: Content exclusion keeps matching files out of Copilot's direct context across inline and Chat, but type and build hints, symbolic links and some Agent modes still leak. It is defence-in-depth, not a guarantee; changes take up to 30 minutes.
| Criterion | VS Code | JetBrains IDEs | GitHub website | Azure Data Studio | Xcode |
|---|---|---|---|---|---|
| Inline suggestions | Excluded | Excluded | No inline surface | Excluded | Not documented |
| Copilot Chat | Excluded | Excluded | Excluded | Not covered | Not covered |
Rules
- Content exclusion applies across Copilot's experiences including Chat, not inline completions only.
- Copilot may still receive indirect semantic information such as type or build details from the IDE despite exclusion.
- Symbolic links and remote filesystem repositories currently bypass content exclusion rules.
- Some editors' Edit and Agent modes lack content exclusion support, so verify coverage before relying on it there.
- Rule changes can take up to 30 minutes to propagate; forcing an IDE settings reload applies them sooner.
- Treat exclusion as one defence layer alongside secret scanning, never the sole control for credentials.
Traps
- Exclusion governs Copilot context only; it does not delete files or alter git history.
- Excluding a build configuration file does not fully hide it - build details can still surface indirectly through the IDE.
- The indicator is not a red icon or a blocking modal: an excluded file shows a diagonal line on the Copilot status icon, with hover text naming the rule.
- Exclusion changes are reviewable through the audit log, not just by asking developers.