What changed
Computer use is now in public preview in the GitHub Copilot CLI and the GitHub Copilot standalone app (macOS and Windows). Copilot can read accessible app content and visual context, click controls, enter and edit text, press keys, scroll, drag, and navigate workflows across desktop applications — including legacy and GUI-only software with no API, CLI, or MCP integration. Not available in the VS Code Copilot extension.
TL;DR
GitHub Copilot Computer Use (public preview, macOS + Windows) lets Copilot automate any desktop application workflow, including legacy GUI-only software, using accessibility APIs and screen-reading rather than requiring an API or MCP server.
Developer signal
The practical unlock is legacy and GUI-only software: Copilot can now drive any application that runs on your desktop, not just those with APIs or MCP integrations. This means automating workflows in CAD software, ERP systems, test-case management GUIs, internal desktop tools, or any other application you currently have to operate by hand. To enable in the CLI: run /computer on; use /computer show to check status, /computer off to disable. In the Copilot app: Settings → Computer Use → Enable Computer Use. On macOS, Copilot will prompt you to grant Accessibility and Screen Recording permissions on first use — these are required for it to see and interact with apps. Organization-managed Copilot accounts can disable the feature via policy. Copilot asks for approval before taking control of an application; you can set "always allow" for apps you use frequently. Best prompt pattern: describe the outcome you want, the app involved, and any constraints ("summarize my unread Jira tickets in Firefox, ignoring anything from before September"). Important: this is public preview in the standalone Copilot CLI and app — the VS Code Copilot extension does not yet have this capability.