GitHub Copilot Computer Use: Setup, Commands & Safety Checklist

Quick answer: GitHub Copilot Computer Use lets the Copilot app and Copilot CLI interact with local desktop applications on macOS and Windows. It can read visible or accessible app content, click controls, type, scroll, drag and move through multi-app workflows. The feature is in public preview, is disabled by default and must be explicitly enabled.[1][2]

What GitHub Copilot Computer Use can do

Computer Use is meant for visual workflows that cannot be completed more reliably through an API, terminal command, filesystem tool, browser tool or MCP integration. GitHub lists examples such as reviewing a legacy desktop application, updating a presentation, entering information into GUI-only software and moving information between applications.[2]

Capability	Example	Control to keep
Read app content	Summarize status information shown in a legacy application	Ask for read-only work and prohibit changes
Click and navigate	Move through a GUI-only workflow	Approve only the intended application
Enter or edit text	Update a presentation or form	Require review before save or submit
Move information	Copy approved data between desktop apps	Define exact source and destination fields
Scroll and drag	Navigate long pages or reorder interface items	Watch for wrong-window or wrong-control errors

GitHub says the Copilot app and Copilot CLI are available with all Copilot plans. Organization-provided CLI access still depends on the organization enabling the Copilot CLI policy, and enterprise administrators can disable Computer Use through managed settings.[3][4]

How to enable Computer Use in the GitHub Copilot app

1. Open the GitHub Copilot app on a macOS or Windows computer.
2. Open Settings.
3. Select Computer Use in the sidebar.
4. Turn on Enable Computer Use.
5. On macOS, grant both Accessibility and Screen Recording permissions. Accessibility lets Copilot interact with controls; Screen Recording lets it inspect application windows when visual context is required.
6. If the macOS permission change is not detected, select Check again.

You can also enter /computer on inside an app session. GitHub documents /computer show as the status check for the Computer Use plugin and MCP connection.[3]

How to enable Computer Use in GitHub Copilot CLI

Open an interactive Copilot CLI session, then use these commands:

/computer show
/computer on
/computer off

/computer show reports whether the bundled plugin, MCP server and associated skills are enabled. /computer on saves the preference and enables the bundled Computer Use plugin. If an organization policy blocks the feature, the CLI reports the managed-settings restriction; a local setting cannot override it.[4]

Troubleshooting commands

If Computer Use is enabled but does not work, GitHub recommends checking the bundled plugin with /plugin and its MCP connection with /mcp list. On macOS, also confirm that the Computer Use helper has both Accessibility and Screen Recording permission.[4]

Copy-paste starter prompts

GitHub says prompts work best when they specify the desired outcome, the applications involved and important constraints.[1] Begin with a read-only task before allowing edits.

1. Read-only application summary

Open [APP NAME] and summarize the status information visible in the main window.
Do not click Save, Submit, Send, Delete, Purchase, Approve or any navigation that changes data.
If login, payment, personal information or an unexpected dialog appears, stop and ask me to review it.

2. Presentation update with a review gate

Open [PRESENTATION APP] and update slide [NUMBER] using the approved text below.
Preserve the existing theme and do not change other slides.
Do not save or export. Stop when the edit is visible so I can review it.

APPROVED TEXT:
[PASTE TEXT]

3. Move information between apps

Read only the fields [FIELD LIST] from [SOURCE APP].
Enter them into the matching draft fields in [DESTINATION APP].
Do not submit the form. Do not copy passwords, payment details, access tokens or unrelated personal data.
Stop when all draft fields are filled for review.

4. Safe GUI test

In [TEST APP OR STAGING ENVIRONMENT], perform this test:
1. [ACTION]
2. [EXPECTED RESULT]
Take no action outside this app.
Do not modify production data.
If the expected control is missing or ambiguous, stop instead of guessing.

Permission controls you should understand

Computer Use follows the tool-permission settings of the surface running the session. When approval is required, you can allow an application for the current session, choose Always allow for future sessions or deny access. An “Always allow” decision is stored locally and applies to both the Copilot app and CLI on that computer. Configured deny rules take precedence.[2]

In the Copilot app, saved approvals appear under Settings → Computer Use → Always allowed apps. Removing an app deletes its approval for future sessions on both surfaces, but it does not revoke access already granted to a running session. Stop or end the active session when immediate revocation is required.[3]

Practical safety checklist

• Prefer a direct tool: use an API, CLI, filesystem operation, browser tool or MCP integration when one can complete the job predictably.
• Start read-only: verify that Copilot can identify the correct app, window and controls before allowing edits.
• Use test data first: trial the workflow in a sandbox, staging account or disposable document.
• Name forbidden actions: explicitly prohibit sending, submitting, deleting, purchasing, publishing or approving unless that is the reviewed task.
• Avoid blanket approval: do not select Always allow for apps containing financial, personal, customer, health or enterprise-sensitive information.
• Keep secrets out of view: close password managers, token consoles and unrelated confidential windows.
• Require a final stop: instruct the agent to pause before any irreversible action.
• Watch the session: review tool activity and interrupt immediately if it opens the wrong app or chooses the wrong control.
• Verify the result: compare changed values against the source before saving or submitting.
• Remove stale approvals: review the Always allowed apps list after the workflow.

These controls matter because GitHub warns that changing interfaces, timing and window state can cause Computer Use to select the wrong control, enter text in the wrong place, repeat an action or fail to continue. GitHub also warns that ambiguous instructions or unexpected on-screen content can trigger unintended actions affecting a device, data or connected account.[2]

How to stop or disable Computer Use

• Copilot app: click Stop or press Esc to interrupt the current operation.
• Copilot CLI: press Esc twice to interrupt the operation.
• Disable in app: Settings → Computer Use → turn off Enable Computer Use.
• Disable in CLI: run /computer off, then /computer show to confirm the plugin and MCP server are disabled.

Stopping an operation and removing a saved approval solve different problems. Stop the running session first, then remove any saved app approval that should not persist.[3][4]

Frequently asked questions

Is GitHub Copilot Computer Use available on Linux?

Not according to the current GitHub documentation. Computer Use is documented for local sessions on macOS and Windows.[2]

Is Computer Use enabled by default?

No. GitHub says it is disabled by default and must be enabled before an agent can use its tools.[2]

Which command enables it in Copilot CLI?

Run /computer on in an interactive Copilot CLI session. Use /computer show to check status and /computer off to disable it.[4]

Why can I not see or enable Computer Use?

Confirm that you are using a local session on macOS or Windows and that the feature is available for your account. For organization-provided access, managed settings or a disabled CLI policy can block it. On macOS, verify both Accessibility and Screen Recording permissions.[4]

Should I choose Always allow?

Use it sparingly. GitHub warns that later actions can control an always-allowed application without asking again and recommends avoiding that option for applications containing sensitive information or supporting high-impact actions.[2]

Is Computer Use generally available?

No. GitHub labels it a public preview that is subject to change.[2]

Last checked: October 3, 2026.

Official sources

1. GitHub Changelog: GitHub Copilot can now interact with desktop apps with computer use
2. GitHub Docs: About computer use in GitHub Copilot
3. GitHub Docs: Using the GitHub Copilot app to interact with desktop applications
4. GitHub Docs: Using GitHub Copilot CLI to interact with desktop applications