What changed
On October 1, 2026, GitHub put computer use into public preview in GitHub Copilot CLI and the GitHub Copilot app on macOS and Windows. Once enabled, Copilot can read accessible application content and visual context, click controls, enter and edit text, press keys, scroll, drag and navigate workflows across desktop applications. GitHub explicitly positions this for legacy and GUI-only software that lacks an API, command-line interface or MCP integration.
Why it matters
Coding agents have mostly been strongest where software exposes files, shells, APIs or structured tool interfaces. Computer use gives Copilot a fallback for the opposite case: applications whose only practical automation surface is their GUI. That can connect development work to browsers, presentations, internal tools and older desktop software without writing a bespoke integration first. The trade-off is a larger action and security surface: GitHub requires approval before Copilot controls an app, macOS requires Accessibility and Screen Recording permissions, and organisations can disable the feature. It remains a public preview, so builders should treat it as supervised automation rather than a stable unattended execution layer.
Copilot gets a GUI fallback when no tool interface exists
Computer use can inspect accessible content and visual context, then click, type, scroll, drag and move through application workflows. GitHub's examples include summarising browser notifications, editing presentation content and moving information through multi-application workflows.
The permission boundary is explicit
Copilot asks for approval before controlling an application. Users can review or reset applications they have chosen to always allow. On macOS the feature requires Accessibility and Screen Recording permissions, and organisation-managed settings can disable computer use.
This broadens what a coding agent can finish end to end
A repository task often ends at a boundary where a developer must use a GUI-only admin tool, browser workflow or legacy application. Computer use lets the same Copilot session attempt that final step instead of requiring an API, CLI or MCP server to exist first.