Microsoft’s ‘software factory’ pitch runs into a very real PC memory limit

Microsoft is pitching Windows PCs as places where Copilot can build software and run AI models locally, potentially reducing cloud use for some work. But TechRadar’s account of the 7 October launch says the largest model needs substantial memory, and several of the features are not yet generally available.

Microsoft AI Watch analysis

What happened

Microsoft CEO Satya Nadella described a vision of PCs where people can build software through Copilot. The company’s launch materials include MAI-Code-1.1 Flash, a 137-billion-parameter coding model, and a Copilot experience that can build apps, dashboards or workflows from a plain-language description. Microsoft says the model has been optimised to run on a PC and that Copilot can hand work to local models.

There are important qualifications. TechRadar says Microsoft’s own engineering material describes automatic routing between local models and the cloud, and states that local inference does not make a session offline. That routing is due to ship at the end of October. Hybrid Copilot features are expected on Copilot+ PCs over the coming months, while Code is rolling out first through Microsoft’s Frontier early-access programme.

The hardware demands are not trivial. TechRadar reports that the on-device model is quantised to 53GB and peaked at 75.5GB of memory at full context on Microsoft’s test machine, a Surface Laptop Ultra. The article says the 128GB configuration costs $5,899 and was not yet available to buy. Those figures are reported by TechRadar from Microsoft’s materials and product information.

Why it matters

Local AI could reduce cloud use and give people new ways to make small, tailored tools. But “runs on your PC” is not the same as “runs on any PC”, and local processing does not necessarily mean a task stays offline. For businesses, the practical questions include which hardware can handle the workload, where data goes, and who maintains software built this way.

That last question is not a footnote. An app that works in a demo still needs updates, support and security checks before an organisation can depend on it. TechRadar cites surveys showing concern among IT leaders about citizen-built tools reaching production, though those figures reflect the studies it names, not a direct measure of Microsoft’s new features.

Our read

The useful story is not that app stores are finished. It is that Microsoft wants Copilot to become a route to making and running software, with local models part of the pitch. That could make experimentation cheaper and more accessible, but the memory requirements, cloud routing and staged rollout put a fairly firm border around the “infinite” factory. A prototype is easy to conjure; a dependable business tool still needs grown-up plumbing.

What to watch

• When local routing and the wider Hybrid Copilot features actually reach users.
• Which PCs can run MAI-Code-1.1 Flash, and how performance compares across configurations.
• Whether Microsoft clarifies when work runs locally and when it uses the cloud.
• What safeguards and support options businesses get before employee-built apps reach production.

Discussion spark: Should businesses encourage staff to build their own small AI-powered tools, or keep software creation behind formal IT approval even if that slows useful experimentation?

not affiliated with or endorsed by Microsoft