Microsoft Copilot Will Gain Local File Actions and On-Device Models on Copilot+ PCs

Microsoft announced on October 7, 2026 that its revamped Copilot experience will gain three Windows-specific capabilities on Copilot+ PCs: access to relevant local context with permission, the ability to perform local PC actions, and access to AI models running on the device. The company says these features are expected to begin rolling out in the coming months, rather than being generally available on every Windows 11 PC today.

This is a different development from the new taskbar Windows Search preview. Search is gaining direct shortcuts for selected settings and workspace actions; the new Copilot proposal is a broader assistant workflow that can use information from files and recent activity, then carry out multistep tasks with user permission. Microsoft has not provided a definitive public release date, universal hardware list or complete list of permitted actions.

In Copilot Home, Microsoft describes retrieving the files a person has been working on and helping turn that material into artifacts ready to share. Its Code experience is intended to help build native Windows applications, run code within supported containment and select local models where appropriate. Autopilot, described as a persistent agent, is expected to combine local context and actions with longer-running work.

An October 8 report by The Verge describes a Microsoft demonstration in which Copilot located documents, renamed and compressed files, and prepared an email. A staged demonstration illustrates intended behavior but does not establish that the full workflow is shipping to ordinary PCs today. Nor does it prove reliability across arbitrary files, programs or accounts.

Microsoft's hybrid-intelligence approach is to use an on-device model for tasks where local compute makes sense and cloud models where additional capability is needed. That can reduce some remote inference work, but it is not an offline-only mode or a blanket assurance that every document involved in a workflow stays on the PC. The company has not specified a complete task-by-task routing policy for the future Copilot rollout.

Privacy and security will depend on the actual consent prompts, file scopes, network behavior, model routing and administrator policies that ship. Microsoft documents separate privacy controls for its consumer Copilot app, including memory, chat history and shared experiences, but those existing settings should not be mistaken for a full technical specification of the upcoming Windows-local agent permissions.

Microsoft also announced experimental local/cloud routing through GitHub HydraFusion for the GitHub Copilot app, CLI and Visual Studio Code later in October. That announcement targets coding-model selection; the Windows Copilot change targets a broader personal assistant working with files, device diagnostics and everyday tasks. A third announcement, Microsoft Execution Containers becoming generally available, concerns the sandbox boundary for agent tool execution. The three are related platform developments, not interchangeable product releases.

Similarly, the redesigned Windows Search preview is beginning in Windows Insider Experimental builds with direct settings actions. Its limited taskbar commands do not imply that the broader Copilot local-file agent is available in that preview. Readers should distinguish the already-started Search test, the later-in-October GitHub routing experiment, and the Copilot+ PC rollout promised for the coming months.

The first meaningful checkpoint is a public preview or release that shows exactly which Copilot+ PCs are eligible, how access to folders and recent activity is granted or revoked, which file changes require confirmation, and whether the user can inspect completed actions. For sensitive documents, a successful demo is not a substitute for verifying permission boundaries and recovery options.

Independent testing should then measure accuracy on real file collections, error recovery after partial actions, local-versus-cloud routing and the latency or power cost of on-device models. Until those details exist, the confirmed story is Microsoft's announced direction and phased rollout—not proven automation reliability, guaranteed offline privacy or a universal Windows 11 upgrade.