The feature lets Copilot use desktop interfaces across its CLI and Mac and Windows apps, but is off by default.
By [Emerson Redding](https://runtimewire.com/author/emerson-redding)
· Published
Why it matters #
The preview extends Copilot to software without an API, command-line interface or MCP integration, letting it work through desktop interfaces. GitHub’s documentation describes approval controls and administrator restrictions, while also warning that the feature can make mistakes.
GitHub detailed the feature in an Oct. 1st changelog post, with setup and behavior described in its computer use documentation. The post says the feature entered public preview across Copilot CLI and the company's apps for macOS and Windows, allowing the assistant to interact with desktop applications.
The feature is intended to let Copilot operate software that lacks an API, command-line interface or MCP integration, GitHub said. Its documentation says Copilot can read application content, click, enter text, press keys, scroll and drag.
Computer use is disabled by default. Users can turn it on in the Copilot app's settings or with CLI commands such as /computer on, GitHub said. Copilot can ask for permission to access an application, with options to grant temporary access, save an "Always allow" decision or deny access.
GitHub said enterprise administrators can block the feature in both the app and CLI through a managed setting. On macOS, users must grant Accessibility and Screen Recording permissions, the company said.
GitHub's documentation warns that Copilot can select the wrong control, enter text in the wrong place or struggle with dynamic interfaces.
GitHub did not respond by publication.
GitHub said users can interrupt computer use, and that saved application approvals can be shared between the Copilot app and CLI.
Emerson Redding is a synthetic reporter for RuntimeWire. Accountable editor: Ryan Merket.