News / Software, Web & Apps
GitHub Copilot expands capabilities with computer use: automating desktop applications under conditions Published on 1 October 2026 by Lawing Tech Newsroom (3 min read)
GitHub Copilot CLI and the GitHub Copilot app are now available in a public preview with a computer use feature capable of interacting with desktop applications on macOS and Windows. This advancement, subject to user approval and system permissions, opens possibilities for automating complex workflows, even in outdated software or applications lacking APIs. According to GitHub, organizations can control its activation via dedicated settings.
Video: GitHub Copilot: Your AI Companion for Every Workflow (GitHub, YouTube)
What is computer use in GitHub Copilot and how does it work?
The computer use feature, now available in public preview for GitHub Copilot CLI and the GitHub Copilot app , enables automation of interactions with desktop applications installed on macOS and Windows. Unlike traditional tools limited to command-line interfaces or development environments like VS Code, this feature extends Copilot’s capabilities to graphical software, whether modern or legacy, as long as they are accessible via screen and keyboard.
Concretely, Copilot can read content displayed on screen, simulate clicks, input text, or execute sequences of actions, all under explicit user control. Before any interaction, the system requires manual approval, and granted permissions can be revoked at any time. On macOS, enabling this feature requires two specific system permissions: Accessibility and Screen Recording , reflecting the sensitivity of the data handled.
With computer use , GitHub Copilot puts the user at the heart of the process, requiring explicit approval before any automated interaction with desktop applications.
Illustrative photo: laptop (Gugalcrom123, CC BY-SA 4.0)
What are the concrete use cases and technical limitations?
GitHub highlights that computer use excels in scenarios where software lacks APIs, CLIs, or modern integrations. For example, a developer could use Copilot to automatically synthesize notifications displayed in a browser like Safari, or update data in a PowerPoint presentation without relying on custom scripts. However, the effectiveness of the feature heavily depends on the precision of the instructions provided: clearly describing the goal, the applications involved, and the constraints significantly improves results.
Limitations include the requirement for a macOS or Windows environment, as well as dependence on system permissions. Organizations can disable this feature via centralized settings, a useful control for sensitive environments where data security is paramount.
How to enable or disable computer use in Copilot CLI and the application?
In GitHub Copilot CLI , enabling computer use is done via the /computer on command, while its status can be checked with /computer show and disabled by /computer off. For the GitHub Copilot application , the process is more intuitive: simply go to Settings > Computer Use > Enable Computer Use to activate the feature. These mechanisms reflect GitHub’s approach to maintaining a balance between automation and user control.
GitHub states that this feature will be integrated into releases from October 1, 2026, for both CLI and application versions, as part of a public preview phase. User feedback will likely guide future improvements.
What this means here: implications for businesses and administrations in West Africa
For businesses and administrations in Benin and West Africa, where technical environments often range between modern and legacy software, computer use could represent a significant productivity gain. For example, teams working with outdated but still widely used management tools could automate repetitive tasks such as report consolidation or data migration without requiring costly overhauls of existing systems.
However, its adoption would depend on several factors: compatibility with local configurations, particularly internal security policy restrictions, and training teams to formulate precise instructions for Copilot. Organizations using open-source solutions or undocumented software could also benefit from this feature to integrate custom tools into automated workflows, provided they comply with system permission requirements.
Finally, the ability for administrators to disable computer use at the organizational level would offer granular control, essential in a context where protecting sensitive data is a priority, particularly for public institutions or financial sectors.
Sources Prepared by Lawing Tech's technology watch from the sources cited. Our editorial charter