On 2026-10-01 GitHub announced Computer Use in public preview for Copilot CLI and the Copilot app on macOS and Windows: agents can drive local desktop apps via accessibility tree/screenshots, clicks, typing, scroll/drag, and cross-app workflows—targeting GUI-only legacy software. Off by default; enable with /computer on or Settings; enterprise policy can block it.

Key Takeaways

🧭

Finished reading? Explore benchmark rankings & pricing

Real-world SWE-bench scores & $20/mo vs API cost break-even calculator

🔬

In-Depth Technical Analysis

Core Background & Industry Pain Points

Many workflows still live in GUI-only legacy apps with no API, CLI, or MCP. Terminal agents can edit repos but cannot drive those desktops. GitHub’s 2026-10-01 changelog puts Computer Use into public preview for Copilot CLI and the Copilot app on local macOS/Windows sessions.

Architecture Highlights & Internals

Per About computer use, the agent reads the OS accessibility tree (and screenshots when needed), then clicks, types, presses keys, scrolls, drags, and navigates across apps. Status via /computer show (bundled computer-use plugin + MCP). Prefer API/MCP/terminal/filesystem/browser tools when available. Tool permissions apply; Always allow is shared across CLI and app on the same machine; enterprise managed settings can disable the feature. macOS needs Accessibility + Screen Recording.

Authoritative Benchmarks & Measured Scores

No official OSWorld/WebArena/CUA-SWE scores in the changelog—do not invent numbers. Product anchors: public preview, off by default, local macOS/Windows only. Risks and limits: Responsible use — Agents.

Developer Hands-on Guide

Enable with /computer on (CLI) or Settings → Computer Use (app); verify with /computer show. Prompt with outcome, apps, and hard constraints. Approve carefully; Esc twice / Stop to interrupt; prune Always allow for sensitive apps; admins decide policy first.