GitHub extended Copilot's Content Exclusions mechanism to Copilot app and Copilot CLI too.
The goal is to prevent code marked as sensitive or unsuitable for AI use from automatically entering the agent's working context.
This sounds like a small change.
For organizations running coding agents with access to large code repositories, it can be a significant security point.
What are Content Exclusions?
An organization can define files, folders or project sections that should not enter Copilot's context.
For example:
- Sensitive code
- Customer code
- Key files
- A project with contractual restrictions
- Sections they do not want sent to the model
The problem is that Copilot agents no longer operate only inside the code editor.
Why expansion to CLI matters
Copilot CLI can work from the terminal.
Copilot app can take broader actions as an agent.
If exclusion rules applied only inside a particular IDE, the same sensitive code could enter context through another interface.
GitHub says Copilot app and CLI now respect Content Exclusions.
This does not mean the code is protected in every situation
It is important not to exaggerate.
A file being excluded from Copilot's ordinary context does not necessarily mean there is no other way information could reach an external tool.
For example:
- MCP server
- Shell command
- Log
- Plugin
- External tool
- Another connection
Content Exclusions are therefore a control layer, not an absolute guarantee.
Other updates in the same release
GitHub also announced that the new Copilot harness reached general availability (GA) in JetBrains.
Agent Merge entered public preview in VS Code.
The capability is intended to let an agent attempt to handle:
- Review comments
- Failed tests
- Merge conflicts
Before merging.
GitHub also added support for additional models in some plans.
Where GitHub is taking Copilot
GitHub's direction is clear.
Copilot is turning from a system suggesting a line of code into one that can:
- Navigate a project
- Run tools
- Check code
- Resolve conflicts
- And work from the terminal.
As autonomy grows, access and exclusion controls also need to expand.
What GitHub has not yet published
It is unclear how far Content Exclusions affect every external MCP server.
It is unclear whether shell commands can indirectly return excluded information.
GitHub did not publish full audit documentation in the announcement allowing every attempt to access an excluded file to be checked.