Windows 11 Copilot+ AI in Settings: Fast On-Device Help for Quick Tweaks

  • Thread Author
Microsoft’s incremental but meaningful upgrade to the Windows 11 Settings experience has just landed in the Beta channel preview — and it makes the OS’s best AI feature noticeably more useful, but only for Copilot+ PCs with the necessary on‑device NPU hardware.

Background​

Microsoft has been folding on‑device AI into Windows 11 throughout 2024–2025, building a layered Copilot ecosystem where some capabilities run in the cloud while higher‑performance, lower‑latency features execute locally on Copilot+ PCs — a hardware class defined by an integrated Neural Processing Unit (NPU) capable of 40+ TOPS. The company’s strategy is deliberate: ship model binaries and framework support in cumulative updates, then enable features selectively by device class, region and account entitlement.
The newest Insider preview (Beta build 26120.6780; Dev build 26220.6780 appears alongside similar work) includes two headlining changes for the Agent in Settings — Microsoft’s contextual AI assistant embedded in the Settings app — plus a handful of related UI polish items (notably a Run dialog dark‑mode fix). These changes are being rolled out under Microsoft’s controlled feature‑toggle model for Insiders and, crucially, are available in full only on Copilot+ PCs.

What changed in this preview​

Two practical upgrades to the Agent in Settings​

The preview improves the Settings agent in two meaningful ways:
  • More actionable search results: When you type a settings query, the agent returns an expanded list of matching results and, where applicable, embeds direct controls (for example, a volume slider or display scaling option) in the search flyout so you can adjust settings without navigating into a nested page. If a requested change cannot be performed (for instance, brightness is already at maximum or a setting is policy‑locked), the agent explains why and shows the appropriate control or remediation path.
  • Recently‑used and recommended settings on the homepage: The Settings home panel can now surface recently modified or commonly recommended toggles with inline actions, letting you quickly revert or tweak a change you just made — a real time‑saver when troubleshooting or reversing experimental tweaks.
These updates are framed as usability and discoverability improvements: the agent is evolving from a search helper to an actionable assistant inside Settings. The goal is fewer clicks, less hunting through nested menus, and clearer explanations when changes can’t be applied.

Other visible touches in the build​

Beyond the Settings agent, the preview includes related UX work that enhances Copilot experiences and general consistency:
  • Click to Do visual cues: Click to Do — the contextual overlay that recognizes text and images on screen and surfaces Copilot actions — will now highlight recognized entities (tables, emails, structured content) when available, making it easier to confirm what the assistant will act on.
  • Drag Tray refinements: The experimental Drag Tray (drag files toward the top of the screen to quickly share or move them) gains multi‑file support and smarter app suggestions, plus an option to move files directly into folders from the tray.
  • Run dialog dark‑mode polish: The Run box (Win+R) now respects Dark mode, replacing the jarring white window that previously broke the visual theme. This is part of a wider push to eliminate unthemed legacy dialogs across Windows.

Why this matters for everyday users​

These are not headline‑grabbing features, but they change the flow of common tasks. For average users — and especially for those less comfortable with nested settings pages — the on‑device agent reduces friction in three ways:
  • Speed: Inline controls and direct actions cut the number of clicks needed to adjust a setting.
  • Clarity: Explanations when a change is impossible avoid dead‑end searches and confusing error states.
  • Recoverability: Recently used options on the Settings homepage make it trivial to undo an accidental change.
That combination makes Settings feel more like an assistant and less like an index of options — a subtle but practical improvement that helps both novice and intermediate users. Independent previews and Microsoft’s own guidance emphasize this utility-first design.

The hardware gating: Copilot+ PCs and why they matter​

All of this convenience has a clear caveat: Microsoft has reserved the full agent experience for Copilot+ PCs — devices with dedicated NPUs designed to run local models at practical speed and power. The official guidance and multiple independent reports indicate an NPU threshold of 40+ TOPS (trillions of operations per second) as the practical minimum for Copilot+ designation, and many Copilot+ systems ship NPUs in the 40–45 TOPS range. Microsoft’s documentation describes this requirement and lists example Copilot+ hardware families.
Why the gating makes sense technically:
  • Latency and responsiveness: Local models running on NPUs deliver near‑instant responses without a round trip to cloud servers — essential for quick settings adjustments and embedded UI controls.
  • Privacy posture: On‑device processing reduces the need to send device state or partial screen content to cloud services for routine tasks.
  • Battery and thermal profiles: NPUs are optimized for inferencing workloads more efficiently than CPUs or GPUs on laptops, allowing sustained AI responsiveness without huge battery penalties.
These benefits are real, but they come with tradeoffs: hardware cost, limited availability, and uneven coverage across the installed base. Not every Windows 11 PC — even recent ones — will be Copilot+ certified. Copilot+ is a hardware-defined experience tier, not simply a software toggle.

Verification of key technical claims​

To ensure accuracy, core technical facts were cross‑checked with Microsoft’s developer and product documentation and multiple independent outlets:
  • Build identifiers and preview channels: Microsoft and community reporting identify Beta build 26120.6780 (and the matching Dev flight 26220.6780) as the cumulative preview package shipping the enablement code for these controlled rollouts. These updates are being staged via the Insider program and may require the “Get the latest updates as soon as they’re available” toggle to increase rollout speed.
  • Copilot+ hardware requirement: Microsoft’s Copilot+ guidance states many new Windows AI features require NPUs capable of 40+ TOPS, and Microsoft lists device families that meet these criteria; independent hardware coverage and device spec sheets corroborate the 40+ TOPS floor.
  • Agent behavior and model locality: Microsoft’s Windows Experience materials explain that the Settings agent uses an on‑device model (a small language model optimized for settings tasks) and can act on settings with user consent; independent reporting and hands‑on previews describe the same behavior.
If any of these items change in Microsoft’s official rollout, or if the company revises hardware thresholds, the actual availability and performance characteristics may differ from today’s preview behavior. Treat any specific timing or region‑coverage claims as subject to Microsoft’s staged enablement model.

Strengths and likely benefits​

  • Practical, incremental AI: The Settings agent exemplifies a low‑risk, high‑utility application of AI. It does a finite set of tasks — find settings, suggest actions, apply toggles — rather than attempting open‑ended generative dialogue. That scope yields a clear benefit: fewer clicks and less confusion.
  • On‑device privacy and responsiveness: By design, Copilot+ experiences prioritize local inference where possible, reducing cloud dependency for simple actions and improving responsiveness. For many users, that means faster results and a better privacy posture for routine modifications.
  • Developer and admin visibility: The architecture and staged rollout let administrators control exposure in managed environments. Microsoft’s guidance highlights admin controls and enterprise considerations for features like Recall and agentic automation — useful for IT decision‑makers thinking about governance.
  • A better onboarding path: For non‑technical users, an agent that does settings changes with permission can reduce support calls and self‑help frustration. Surfacing recently modified settings is especially helpful for people who tinker and then want to revert changes.

Risks, limitations and enterprise concerns​

  • Fragmented experience across the installed base: Because Copilot+ is tied to specific hardware, millions of Windows users will not see the full agent experience. Features will be inconsistent across devices and channels until Copilot+‑capable silicon becomes far more common. That fragmentation raises support headaches for help desks and increases the complexity of documentation and training.
  • Potential governance and automation risk: An agent that can apply settings changes on behalf of users — even with consent — adds a new automation surface to manage. Organizations must decide whether to allow such automation on managed devices and under what policies. The risk is not only accidental misconfiguration but also a broader need to tie AI agent actions into existing change control and compliance workflows.
  • Privacy and indexing concerns with related features: Though the Settings agent itself largely acts on system preferences, companion features in the Copilot suite (Recall, Click to Do) interact with on‑screen content and snapshots. Those systems are marketed as local and encrypted, but they still raise legitimate questions about retention windows, Windows Hello gating, and policy control in enterprise contexts. Admins and privacy teams must evaluate these carefully before enabling them broadly.
  • Dependence on staged rollouts and server flags: Microsoft’s controlled feature‑rollout approach means that even eligible Copilot+ PCs may not receive features immediately; server‑side flags and regional gating determine exposure. That uncertainty complicates testing and internal rollout plans for organizations trying to pilot features.
  • Not a substitute for stronger UI consistency: The fix to the Run dialog dark mode is welcome, but it’s also a reminder that Windows still contains legacy surfaces that need theming work. The agent improves discoverability, but it doesn’t address an underlying inconsistency problem across old and new UI layers.

Practical testing and deployment guidance​

For individuals and IT teams planning to try the preview or prepare for broader Copilot+ rollouts, these steps and precautions are recommended:
  • Enroll a small, clearly documented pilot group of Copilot+ hardware that meets the 40+ TOPS guidance and is used for testing only. Confirm firmware and driver currency.
  • Use the Windows Insider channels (Dev/Beta) for controlled previews and enable the “Get the latest updates as soon as they’re available” toggle to increase the odds of seeing staged features. Verify builds (winver) and KB identifiers before testing.
  • Test agent actions under both standard user and managed (Group Policy / Intune) configurations to confirm consent flows and admin blocking behavior.
  • Document and publish internal guidance about what agentic automation is allowed on managed devices (for example, disallowing automatic changes to security settings).
  • Evaluate telemetry and support workflows to capture failures, misapplied settings, or unexpected agent behavior — these will be valuable feedback to Microsoft during the Insider flight.

What to watch next​

  • Expansion of the agent to other surfaces: The Settings agent is a natural first testbed because its scope is narrow and the actions are discrete. Microsoft’s broader roadmap suggests similar agentic surfaces could appear elsewhere (Start, File Explorer, contextual apps) as on‑device models become more pervasive. Expect Click to Do and Copilot Vision to land deeper in workflows, but expect staged, gated availability.
  • Model improvements and localization: Current previews are often English‑first. Look for broader language support and improved small language models tuned for local tasks — Microsoft’s Windows ML and Windows AI Foundry efforts underpin this work.
  • Further dark‑mode and UI polish: Dark mode consistency remains a multi‑month effort. The Run dialog fix is a sign of progress, but legacy dialogs and some control surfaces are still being reworked. Expect more incremental theme polish in future updates.
  • Hardware variety for Copilot+ certification: Initially Copilot+ PCs were Snapdragon‑centric, but Intel and AMD silicon with capable NPUs (Ryzen AI, Core Ultra families) are already being positioned to meet Copilot+ thresholds; more certified hardware will broaden availability and reduce fragmentation. Keep an eye on OEM certification lists and Microsoft’s Copilot+ guidance.

Critical verdict​

The Settings agent improvements are a pragmatic, user‑centric application of AI in Windows 11: small, targeted, and immediately useful. They show Microsoft iterating toward a model where AI reduces friction for common tasks rather than adding flashy but brittle features.
However, the Copilot+ gating and staged rollout model introduce fragmentation and governance complexity. The user experience is compelling on qualifying hardware, but the broader installed base will lag. For enterprises and IT teams, the agent is promising but requires policy, testing, and change‑management work before enabling widely.
In short: the feature is a genuine usability win for Copilot+ PC users and a strong signal of Microsoft’s direction — but it also underlines the real-world tradeoffs of hardware‑gated AI in a heterogeneous PC ecosystem.

Final thoughts and practical takeaways​

  • If using or buying a Copilot+ PC (40+ TOPS NPU), expect the Settings agent to become a daily convenience: faster fixes, clearer explanations, and more reliable in‑place controls.
  • If managing a fleet, plan for a phased pilot: validate consent models, define admin blocks for agent automation, and document support flows for mixed‑estate users who do and do not have Copilot+ hardware.
  • If you’re on a standard Windows 11 PC: the agent experience will remain limited or unavailable until compatible NPUs spread. You will still see incremental UI fixes (dark mode polish) and possibly cloud‑assisted Copilot capabilities, but the low‑latency, on‑device agent is Copilot+‑centric for now.
These Settings improvements are a practical illustration of what an AI‑assisted OS can and should be: helpful, narrowly scoped, and integrated into the flow of work. They are not yet universal, but they offer a preview of a future where the OS itself helps you do more, faster — provided your PC has the horsepower to run it locally.

Source: TechRadar Windows 11’s best AI feature just got better – but you’ll inevitably need a Copilot+ PC to use it