Microsoft unveils new Copilot, featuring Home, Code and Autopilot

memo.tyoshida.me reported that Microsoft unveiled a new Copilot on September 25, 2026. The article introduces features including Home, Code and Autopilot.

Home, Code and Autopilot, as described in the article, position Copilot as a product spanning the entry point to work, content creation and task execution. Companies considering adoption need to examine not only individual features but also the scope of tasks they can delegate and how people can review the results.

The announcement points to a design that seeks to extend Copilot beyond one-off question-and-answer interactions, bringing the start of work, the creation of deliverables and ongoing task execution into the same product family. The article's Home, Code and Autopilot features represent different stages: entry, creation and delegation. However, the materials provided do not establish how these features work together or which users can access them, and when. The presence of multiple feature names should be evaluated separately from the question of whether an entire business process can be automated end to end. In FANUC and Microsoft partner on data utilization, we reported on efforts to use operational and business data with Copilot and other tools. The current article describes the features of the Copilot app; it does not indicate a direct connection with FANUC's initiative or show that Copilot can operate factory equipment. The former concerns the data being used and business integration, while the latter organizes product features available to users; they should be viewed as separate layers. The industry implication is that AI's value may need to be measured not only by model response performance but also by which stages of work it handles and where deliverables are managed. In particular, if creation and autonomous execution features are offered within the same product family, companies will need to assess permissions, approvals and points for human intervention across the entire workflow, rather than feature by feature. This is an issue suggested by the product structure; the actual scope of integration and control mechanisms have not been confirmed. The next points to verify are the availability terms for each feature in the official announcement, the business environments they support, the permissions and stop controls users can configure, and how execution results can be checked. The materials provided are a secondary article and do not include the official announcement, so the features' specifications and availability dates cannot be treated as confirmed. See the original source for details.