{"version":"2.1.242","anchor":"computer-use-guidance-is-now-windows-aware-and-separates-scr","canonical_anchor":"computer-use-guidance-is-now-windows-aware-and-separates-scr","heading":"Computer-use guidance is now Windows-aware and separates screen takeover","tier":"notice","area":"Computer Use","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/computer-use-guidance-is-now-windows-aware-and-separates-scr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Computer-use guidance is now Windows-aware and separates screen takeover\n\nComputer-use guidance now names File Explorer on Windows and says elevated programs must come back to you.\n\n**What**\n\nThe instructions for requesting computer access change by platform. On Windows they name File Explorer and warn that elevated programs, such as Task Manager, UAC prompts and admin installers, cannot be driven at all and should be handed back to you. They also state that granting access is not the same as granting screen takeover.\n\n**Details**\n\n- The stated reason on Windows: Windows blocks input sent from a lower-privilege process to a higher-privilege one, so no grant can work around it.\n- Screen takeover has its own consent card, raised automatically the first time a display-wide tool runs after background work.\n- App-scoped tools are described as able to run in the background but unable to reach menu-bar items, hover states, context menus or canvas drags.\n\n**Evidence**\n\n`cannot be controlled even when granted: Windows UIPI blocks input from lower-integrity processes.`\n\n- Area: Computer Use\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}