Microsoft Copilot to Act on Local Files on Windows PCs

What happened

Microsoft is giving its Copilot assistant greater control over Windows PCs, allowing it to organise and change local files and to run certain tasks using on-device AI models. According to Computerworld's reporting, the changes were outlined at Microsoft's Hybrid Intelligence event.

Microsoft said three new Copilot capabilities will reach Copilot+ PC users "in the coming months." The first lets Copilot access local files and recent user activity, giving the assistant more context for its outputs. The second allows Copilot to carry out actions on a device, such as moving files and changing settings. The third was not detailed in the material available to us.

Speaking at the event, Jacob Andreou, Microsoft EVP, Copilot, described the level of control in terms of user parity: "It has the same level of the ability to control and change things that I do as a user, but always with permission." The capability is similar to Copilot Actions, an experimental feature Microsoft has already tested.

Why it matters

The significance lies less in any single feature than in the direction of travel. An assistant that can read local context and act on a device moves AI from answering questions to completing work inside the operating system. For organisations, that changes the question from "what can the model say?" to "what is the model permitted to do, and how is that visible?"

Microsoft's framing also points to a hybrid architecture, combining on-device and cloud processing. Its stated aims are to help customers reduce AI costs and keep more control over data. For leaders in digital transformation, this suggests that where a workload runs may become a design decision as important as which model powers it, with consequences for cost, privacy and the employee experience.

The Renascence take

Most coverage will focus on what Copilot can now do. The more important issue is how people will decide to let it do it. Permission is not a single switch; it is a sequence of moments in which a user sees what is about to change, trusts the outcome and can reverse it.

The real product here is not file access but the permission experience. Every "allow" prompt is a small service encounter, and users will calibrate their trust in Copilot by how clearly it previews, explains and undoes actions. Operators should design for that before rollout: scoped permissions, plain-language previews, visible activity logs and easy reversal. Treat the first wrong file move as the moment that determines whether people ever grant the second permission.