On this page3 sections
The status you need is in an old administration console. No useful API, no command-line route, no Model Context Protocol integration connecting it to an agent. It is just the app somebody opens and clicks through. GitHub Copilot’s computer-use preview gives that familiar desktop work another possible operator.
The October 1 release added desktop interaction to the existing Copilot app and CLI on macOS and Windows. It did not launch a new app or give a cloud coding session control of your desktop.
Two similar records make a useful first test
Copilot uses accessible application content, visual context and interface actions together, as the concept reference explains. That lets it work with screens, but screens can change: a control moves, a selection shifts, a different record opens. Where an API or command-line tool is available, its explicit inputs and responses can avoid some of that ambiguity.
Imagine a test console with two synthetic incidents. DEMO-17 says “Investigating”; the neighboring DEMO-71 says “Resolved.” A platform engineer asks for DEMO-17’s status, naming both the console and the record, without authorizing any edit. If the answer comes back “Resolved,” opening the selected record may reveal the mix-up. These are invented test records, not results from a Copilot trial.
After establishing the target, a later test could authorize changing only DEMO-17 to “Monitoring.” The agent-action approach keeps two permissions separate: controlling the app and making this edit. Neither guarantees the correct record was selected or the change saved. Read the destination record to establish that.
Suppose the reply disappears just after Save. The record may already say “Monitoring.” Another edit cannot tell you what the first one did; reading DEMO-17 again can. If the console cannot provide a trustworthy result, leave the operation unresolved for a person to reconcile rather than guessing from the silence.
Get the local connection working first
Before that test can happen, the local connection has to work. Computer use is disabled by default. In the app, enable it under Settings, Computer Use, for local sessions. macOS also requires Accessibility and Screen Recording permissions. The announced platform scope is macOS and Windows, not Linux.
The CLI guide uses /computer on to enable the CLI integration and /computer show to inspect it. An organization policy can still block a managed subscriber. Running the enablement command again does not override that policy.
If the console is unavailable, start with the connection rather than asking why the incident was misread. /computer show displays the bundled plugin, MCP server and skills; /permissions show displays the active permission mode. GitHub’s troubleshooting guidance points to /plugin and /mcp list for integration or connection trouble. A working connection gets Copilot to the interface; selecting DEMO-17 is the next part of the job.
Stopping a click is different from ending access
Now imagine seeing Copilot move toward DEMO-71. To interrupt the current operation, the app guidance provides Stop or Esc. That interruption does not reveal whether an earlier save succeeded. To revoke this session’s access, end the session. Removing a saved application approval affects future app and CLI sessions on the machine, but does not revoke one already running.
Do not rely on an assumed confirmation prompt to catch the wrong record. Prompts depend on tool-permission settings, CLI mode, saved approvals and managed deny rules. Look at the active mode so you can choose the control that does what you intend: stop this operation, end this session, or change an approval for a later session.
For the authorized edit, the useful closing picture is concrete: DEMO-17 shows “Monitoring,” and the session controlling the console has ended. A missing observation remains missing even if the final message sounds certain. The old console still has no useful API, but a click followed by silence no longer has to be mistaken for a completed job.
Source context
Source links appear within this article. Read them alongside the author’s analysis and evaluate the guidance against your environment.
Report an error or outdated detail