The Pulse
Microsoft Gives Copilot Permission to Act on Windows PCs
Microsoft says Copilot+ PCs will let Copilot use local file context, take actions across Windows and run some AI models on the device. The features are expected to begin rolling out in the coming months, while new taskbar Search actions sta
AI.info Team · Written with AI ·
Copilot will be able to use local files, organize them and take other actions across Windows on Copilot+ PCs, Microsoft announced October 7. The changes expand the assistant beyond answering prompts: with a user’s permission, it can draw on recent activity and work directly with the PC, while using local AI models for some tasks.
Microsoft calls the approach “hybrid intelligence,” combining processing on the computer with cloud-based AI when needed. The company says the Copilot features are expected to begin rolling out to Copilot+ PCs in the coming months; availability and timing may vary by device, market and silicon platform.
“With your permission, Copilot will be able to use local context from your PC, take action on your behalf, and tap into local models, bringing you more capability while helping your tokens go further.”
Pavan Davuluri, executive vice president, Windows + Devices, Microsoft
Copilot moves from reading files to acting on them
Microsoft outlined three capabilities: local context, local actions and local models. With permission, Copilot can use relevant files and recent activity; its actions can include organizing files, checking device diagnostics, troubleshooting, coding and completing workflows on the PC. The company says Home can draw on files a user has been working on to help prepare materials for collaboration.
The same approach extends to Code and Autopilot, Microsoft’s persistent personal-agent experience. Code can use local models and Microsoft Execution Containers when creating Windows apps or running code. Autopilot can combine PC context, local models and actions in its workflow, though Microsoft did not give a specific launch date beyond “the coming months.”
Local processing is part of Microsoft’s cost pitch
Microsoft says local models can handle suitable tasks on the PC while Copilot uses cloud intelligence when needed. The company frames that split partly as a way to manage AI costs: its Windows post says customers’ needs are outpacing what cloud budgets can support. It also reports more than two trillion inferences run locally each month across Copilot+ PCs, and says more than 40 percent of laptops being built for business are Copilot+ PCs.
Those figures describe Microsoft’s overall Copilot+ PC usage and business-device pipeline, not a measured result for the new Copilot features. The announcement does not specify which models or tasks will run locally on each device, or how users will choose between local and cloud processing.
Windows Search gets taskbar actions first
Separately, Microsoft is adding actions to Windows Search, so users can issue commands from the taskbar without opening another app. Examples include switching to dark mode, turning on Do Not Disturb, muting audio, arranging windows and sending a text. The actions begin rolling out to Windows Insiders in the experimental channel on October 7.
Microsoft also plans an optional integration that places Copilot answers inside taskbar Search, with a route to the full Copilot app for longer conversations. That experience is slated to start reaching select markets later in 2026. The Search actions and Copilot’s local-file capabilities are related parts of the announcement, but Microsoft describes them as distinct features with separate rollout plans.
Microsoft’s execution boundary sets limits for agents
Microsoft also made Microsoft Execution Containers generally available on Windows 11. The separate platform feature lets developers and IT administrators define which files and network destinations an agent can access, with those policies enforced while it runs. Microsoft says the policy remains outside the agent’s control, so an agent cannot grant itself additional access.
The guardrail addresses a basic trade-off in giving software agents more authority: access can make tasks useful, but should be limited to what the task requires. Microsoft has not said that every new Copilot action will run inside an execution container. Its announcement leaves practical questions about permission prompts, task-level controls and the timing of the Copilot rollout to be answered as the features reach users.