Microsoft Will Let Copilot Use PC Files and Take Actions With Permission
The coming Copilot+ PC features connect Home, Code and Autopilot to local context and models. Agent access controls are available now.
Loading page…
The coming Copilot+ PC features connect Home, Code and Autopilot to local context and models. Agent access controls are available now.
Listen to this story
Microsoft is adding PC-file context, computer actions and local model access to Copilot, with a rollout on Copilot+ PCs expected over the coming months. The shift makes Copilot more capable of completing tasks inside Windows, while keeping local and cloud computing available as needed; Microsoft’s tax-file example used local processing, but the company did not promise that every workflow will stay offline. For organizations, agent access controls are available sooner than the new Copilot features.
Microsoft Execution Containers became generally available on Windows 11 on October 7, enforcing organizational limits on files and networks an agent can access.
GitHub’s HydraFusion routing for local Windows models is due in experimental preview later in October in GitHub Copilot, its command-line tool and Visual Studio Code.
The Surface Laptop Ultra, equipped with Nvidia RTX Spark, is priced at $2,599 and begins shipping October 16; the Surface RTX Spark Dev Box ships to U.S. customers in November.
Copilot will be able to use files and recent activity on a PC, then act on the user’s behalf with permission. Microsoft announced those capabilities on October 7, 2026, alongside local AI model access. The features are expected to begin rolling out on Copilot+ PCs over the coming months—not become available immediately.
Microsoft’s Windows announcement describes three additions: local context, local actions and local models. Context includes relevant files and recent activity. Actions include organizing files, checking device diagnostics, troubleshooting problems, coding and carrying out workflows directly on the computer.
These capabilities build on Copilot’s recently introduced Home, Code and Autopilot experiences, rather than introducing those modes for the first time. Microsoft describes the Windows integration as a way to bring information from the device into each mode and let more work happen there.
At the event, Copilot chief Jacob Andreou offered a concrete example: gathering the files needed for taxes from different parts of a laptop without accessing the cloud. Microsoft presented that as a task that does not require heavy cloud computing, not a promise that every Copilot workflow stays offline.
Microsoft Execution Containers, or MXC, lets organizations specify which files and networks an agent can access. Those policies are enforced while the agent runs. Microsoft says its Code experience will use MXC support to contain code execution.
The Windows design also separates agent identity from the person using the device, so IT can identify which agent acted. Management tools including Agent 365 and Intune connect that activity to organizational policies and monitoring. Microsoft frames these controls around agents that can use tools, write code and act across systems without someone watching every step.
Microsoft calls the approach hybrid intelligence: tasks can use models on the PC or reach the cloud when needed. A related coding rollout extends GitHub’s HydraFusion routing system to local Windows models. That integration is due in experimental preview later in October in the GitHub Copilot app, its command-line tool and Visual Studio Code.
The accompanying Surface Laptop Ultra uses Nvidia RTX Spark and is priced at $2,599, with availability beginning October 16. Microsoft also opened preorders for the Surface RTX Spark Dev Box, scheduled to ship to U.S. customers in November.
Loading discussion...
Join the conversation
Explain what would make that access worthwhile—or too intrusive.
Be the first to share a perspective or an experience.
Reader comments
Newest comments first. Replies stay oldest first.