GitHub puts Copilot computer use in public preview
GitHub announced that Copilot can interact with desktop applications through computer use, a capability now in public preview in Copilot CLI and the GitHub Copilot app for macOS and Windows.

Key takeaways · 4
- 01
Check whether your team’s target apps are accessible through a graphical interface, since GitHub says computer use can help with software that lacks an API, command-line interface or MCP integration.
- 02
In Copilot CLI, enable the feature with `/computer on`, check its status with `/computer show`, and turn it off with `/computer off`.
- 03
In the Copilot app, enable computer use in Settings under Computer Use, or use `/computer on`.
- 04
Plan for app approval and, on macOS, Accessibility and Screen Recording permissions before trying a workflow.
What GitHub announced
GitHub dated its announcement October 1, 2026, and said Copilot can interact with desktop applications through computer use.[1] The feature is in public preview in Copilot CLI and the GitHub Copilot app for macOS and Windows.[1] GitHub describes the capability as extending Copilot automation to legacy and GUI-only software, including programs that have no API, command-line interface or MCP integration.[1]
How the interaction works
GitHub says Copilot can read accessible app content and visual context, then click controls, enter or edit text, press keys, scroll and drag.[1] It can also navigate workflows across applications.[1] GitHub’s examples include summarizing browser notifications, updating presentation content and moving information through a desktop-application workflow.[1] To request a task, GitHub advises describing the desired outcome, the applications involved and any important constraints.[1] For work teams considering the preview, that guidance suggests spelling out the intended result and boundaries rather than simply naming a sequence of clicks.
Controls, permissions and setup
GitHub says Copilot asks for approval before controlling an app.[1] Users can review or reset apps they have chosen to always allow, and organization-managed settings can disable computer use.[1] On macOS, setup guides users through granting Accessibility and Screen Recording permissions.[1] In Copilot CLI, users can enable the feature with `/computer on`, check its status with `/computer show`, or disable it with `/computer off`.[1] In the Copilot app, users can enable it through Settings, Computer Use and the Enable Computer Use toggle; GitHub also says `/computer on` works there.[1]
What remains unspecified
The announcement establishes a public-preview rollout for Copilot CLI and the Copilot app on macOS and Windows, but it does not list a price or subscription tier.[1][2] It also gives no general availability date, and Technobezz reported that Linux support was not mentioned.[2] Those gaps matter when teams are deciding whether to pilot the feature across a mixed operating environment or budget for wider use. Jeremy Longworth described computer use as a capability that needs control.[3]
Computer use could make automation practical for workflows trapped in desktop interfaces, not just tools with APIs or command-line access. Professionals evaluating it should weigh that potential against app permissions, approval controls and the unanswered questions about pricing, broad availability and Linux support.
Why it matters
Put this to work — one session a day, built for your industry.
Create a free account for a daily session — eight questions and one real-work challenge, on the news that affects your role.
Start freeHow this developed
2 October 2026
GitHub puts Copilot computer use in public preview