Microsoft’s Own Coding Model for Local Use

The coding brain chosen for the desk is not from OpenAI. It is Microsoft’s own model, MIA Code 1.1 Flash (also referred to as Maya Code Flash). This is a 137-billion-parameter coding model with a 256K context window. It has been squeezed down almost 80 percent so it can fit onto a laptop and is now optimized to run on your PC.

GitHub Copilot can hand off a lot of the work to the local model through hybrid intelligence. Hybrid means the system is partial cloud and partial local. With code and Copilot, the idea is that you can essentially build any software you need on your desktop without any cloud token spend. At the same time, the hybrid approach keeps Microsoft’s involvement in place.

Performance Claims and the Memory Reality

On stage, Microsoft showed a slide claiming up to 6.2 times faster performance than a MacBook Pro. The tiny print noted that this was based on preliminary testing by NVIDIA. The catch is that the coding models peak out at 75 gigabytes of memory. A Surface with 24 gigs is listed in the $25,000 range in the discussion, while the 128-gig configuration is described as 5,900 (with other references to a high-end Surface Pro around 59,000 and nearly six grand for the top memory option). Microsoft’s own developer page indicates the router moves up to 20 percent of Copilot’s work to local models. In a live demo, the hard prompt still went to GPT-6 Luna in the cloud while small subagents ran on the local machine. The grunt work that burns most tokens is what Microsoft wants running on hardware you buy, using a model Microsoft owns.

NVIDIA’s Partnership and the Hardware

Jensen described how Windows sparked a platform shift that created a new industry for NVIDIA. The company invented programmable shading GPUs for DirectX, which led to CUDA. It then partnered to bring GPU supercomputers to Azure, which helped OpenAI train GPT. That collaboration inspired the effort to reinvent Windows for the age of personal agents. Four years and thousands of engineers went into the work between the two companies.

The new devices include the Surface Laptop Ultra, a 15-inch machine powered by the NVIDIA RTX Spark Superchip with up to 128 gigs of unified memory. RTX Spark puts NVIDIA’s Grace ARM CPU and Blackwell RTX GPU on a single Superchip. The top configuration has 20 CPU cores and 6,000 CUDA cores. A lower 18-core model drops to 51 GPU cores and is associated with 24- or 32-gig options. At 32 gigs with the higher core count, the setup can run a model like QUEN 3.8 at 27 billion parameters pretty well. The 24-gig version will not get you there, but 32 gigs plus roughly 5,000 cores supports a solid 27B run. Because the CPU and GPU share unified memory, a large AI model can use far more than the VRAM it would typically sit on. Plenty of disclaimers appear in the fine print.

Security, Sandboxes, and Who Controls the Agent

An agent on your PC runs with your access, your files, your emails, and your logins. Microsoft made its own sandbox—Microsoft execution containers—generally available on Windows 11. Codex from OpenAI already supports it, and Cloud Code is on the way. When both Sam and Dario have to plug into Microsoft’s sandbox to run on Windows, the question of who the landlord is becomes relevant. Security is described as foundational, bringing Windows and Agent 365 together so agents can stay secure. The official positioning calls Windows the most secure platform for agents, even though Windows has not always held that reputation.

The Hedging and the Double-Dip

Microsoft is hedging off OpenAI one box at a time. The company that spent years tied closely to Sam Altman is now putting its own model on the machine for a portion of the work. Sam keeps the hard questions while Microsoft goes after the volume. Jensen gets paid either way: the same chips that helped train GPT in the cloud now sit inside the laptop. NVIDIA sells the shovels on both sides of the fight. Over half a million people have already seen related discussion of the announcement.

Local AI as Infrastructure You Own

The broader thesis is that local models, a harness around an agent, and a sandbox on hardware you own put control in your hands. Microsoft’s announcements highlight thousands of actions from the taskbar on one laptop, with a bigger desktop available for heavier grunt work. Hybrid intelligence brings frontier capability to Windows locally and supercharges Copilots. At the same time, the 20 percent local figure and the continued cloud path for harder tasks show the limits of the “unmetered” claim.

People who have been building on local models for well over a year see the value in machines that keep data on the device rather than continuously pumping it to the cloud. Current high-end setups already include RTX cards such as a 5090 paired with a 3060 or a 3090 that remains relevant years later. The new unified-memory Windows hardware raises the possibility of running something like a 27B model comfortably and pairing it with local-first tools. One open-source approach already in use is OpenMonoAgent.ai: a terminal-native AI coding agent that runs entirely on local LLMs, is sandboxed by default, Docker-native, mounts the project with permission gates on destructive operations, and offers zero API costs and zero telemetry. It has been positioned as local-first and unlimited-token from the start.

Conclusion

Microsoft’s event with NVIDIA frames a new chapter for Windows in which every PC becomes a place where agents can work securely on your behalf. The company is pairing its own compressed coding model, hybrid handoff of Copilot work, and new RTX Spark hardware with its execution containers. NVIDIA’s chips sit on both sides of the cloud-training and local-inference equation. The practical outcome is more work staying on hardware the user buys, even while hard prompts still route to the cloud and memory requirements remain high. Whether that leads to broader local ownership of AI infrastructure or simply another set of Microsoft-controlled devices is the question the announcements leave open.