On 1 Oct 2026, GitHub put computer use into public preview in Copilot CLI and the Copilot app on macOS and Windows. Copilot can now click, type, scroll, and drag through desktop apps — including legacy and GUI-only tools that never grew an API, CLI, or MCP. Freelancers already juggling Cursor, Claude Code, Codex, or Copilot for code need a calm decision, not another model ladder.
This is a Try desktop control / Skip keep API-MCP-CLI / Wait / Stay approvals-tight sheet. OpenAI Agents meters stay on the Agents API freelancer budget post. Cursor folder habits stay on Cursor Projects. Office Copilot seats stay on Microsoft 365 Premium Copilot buy-or-skip. OpenShell is a complementary outside-agent sandbox for filesystem and network policy — not desktop GUI clicks. Here the only question is whether GitHub Copilot’s own computer use earns one constrained, non-secret GUI workflow this week.
Affiliate disclosure: some tool or platform links may later be affiliate or referral. Product facts below are from GitHub’s 1 Oct 2026 Changelog, computer-use concepts and how-tos, and Copilot plans docs as of 2 Oct 2026 (SAST) — re-check public-preview status, OS support, and org policy toggles before you change a client workflow. Not legal advice; not a guarantee of clients, savings, or income.
What shipped 1 Oct 2026 — computer use in plain English
GitHub’s Changelog and About computer use docs are blunt: computer use is in public preview and subject to change. Surfaces are GitHub Copilot CLI and the GitHub Copilot app. OS for computer use: macOS and Windows, local sessions only. The Copilot app itself also runs on Linux, but the computer-use callout is macOS and Windows — Linux freelancers get an honest Wait on this sheet, not a pretend enable path.
When enabled, Copilot can read accessible app content and visual context, click controls, enter and edit text, press keys, scroll, drag, and navigate workflows across applications. The aimed gap is legacy and GUI-only software with no API, CLI, or MCP. It is disabled by default. You stay in control: Copilot asks for approval before controlling an app; on macOS it walks you through Accessibility and Screen Recording; org-managed settings can disable the feature so a local enable cannot override policy.
Plan list prices on the plans page still read Copilot Pro $10, Pro+ $39, and Max $100 USD per month for individuals (Business and Enterprise are seat rows). Computer use is a surface feature inside those plans — not a separate SKU invent. Do not invent per-click credit burn for this sheet; meter whatever your account already shows.
GitHub’s own preference order
The concepts page tip is the freelancer rule worth tattooing next to /computer on: if an API, MCP server, terminal command, filesystem tool, or dedicated browser tool can finish the task directly, that tool usually gives more structured information and more predictable results. Computer use fills the gap when those are missing. Prefer the structured tool first. Treat GUI control as the last-mile option for software that never grew a better interface — not as the new default for every job.
Try computer use now — when GUI control earns a seat
Give it a seat when one recurring client workflow is trapped in a desktop GUI with no API: an expense tool, legacy CRM, old admin panel, or presentation polish that still needs a human at the keyboard for approvals. Outcome + apps + constraints in the prompt beat “go click around.” GitHub’s own how-to example is the right shape: open the named app, summarize status, do not change values or submit forms. That constrained shape is how you learn whether computer use saves babysitting time or just adds approval friction.
It also earns a seat when you already pay for Copilot Pro, Pro+, Max, Business, or Enterprise and you already use Copilot CLI or the Copilot app weekly. Flipping computer use on a plan you never open is noise. CLI enable is /computer on (with /computer show and /computer off); the app path is Settings → Computer Use → Enable, or the same slash command in a session. On macOS you must be willing to grant Accessibility and Screen Recording for the helper. Stay at the keyboard for the first sessions — Allow for the session, not Always allow, until you know which apps are safe to remember.
Joburg packaging only: many freelancers keep client admin portals, banking UIs, and coding tools on one Windows or Mac laptop. That is why a named, non-secret GUI try matters — not invented ZAR bills or “minutes saved” averages. One logged row on a throwaway workflow beats a launch slogan.
Skip — keep API / MCP / CLI / browser tools
Skip when the task is already solvable with MCP, terminal, filesystem, or a dedicated browser tool. That is GitHub’s tip, not Mr1Tech preference cosplay. Skip when the work is coding-only inside an IDE or CLI with no GUI handoff — computer use does not earn a seat just because Copilot can now click.
Skip when you refuse to approve desktop control on a machine that holds banking, payroll, or other people’s PII. Skip when your daily driver is Linux — computer use is not available there even though the Copilot app runs on Linux. Skip when freelancing is chat-only with no Copilot CLI or app habit; buying a GUI-control surface you will not babysit is the wrong layer. Agents meters and Cursor Projects stay on their own posts — different products. M365 Copilot is an Office seat buy/skip, not GitHub Copilot CLI or app desktop control — keep that framing on the M365 sheet. Do not rematch OpenShell as “the same feature”: OpenShell tightens what an agent can touch on disk and network (outside-agent sandbox); computer use is Copilot clicking inside apps you already see. Complementary security layer if you need both — never a rewrite of that sheet here.
Wait / stay tight — when not to flip Always allow
Wait while public preview still means the product can change. Wait when org or enterprise managed settings disable computer use — local /computer on cannot override that policy. Wait when you will not babysit approvals for the first constrained runs. Ambiguous prompts plus unexpected on-screen content can cause unintended actions; GitHub’s warning is explicit that computer use is not a substitute for human judgment and can affect device, data, or connected accounts. Interfaces also drift across app versions and window states — wrong control, wrong text field, or a repeated click are documented risks, not edge folklore.
Stay approvals-tight when you do try it. Approval choices are Allow (this session), Always allow (saved), or decline. Deny rules win over saved approvals. Always allow is stored locally and applies to both CLI and app on the same machine — so a casual Always allow in the CLI is also an Always allow in the app. Avoid Always allow for apps with sensitive data or high-impact actions. Review the Always-allowed list in app Settings → Computer Use and remove apps you no longer trust; removing deletes the saved approval for future sessions on both surfaces, but does not revoke access already granted in a running session — Stop or Esc that session first. Interrupt with Esc twice in the CLI, or Stop / Esc in the app. Prefer per-session Allow until a throwaway workflow proves the pattern.
Buy/skip matrix (sheet)
| Situation | Try desktop control | Skip — keep API/MCP/CLI | Wait (Linux / org / no GUI pain) | Stay approvals-tight |
|---|---|---|---|---|
| Legacy expense / CRM GUI, no API | Yes — one named non-secret flow | If MCP/CLI already ships it | — | Allow session only first |
| Multi-app copy between desktop tools | Maybe — constrain the prompt | If a script or API exists | — | No Always allow on money apps |
| Pure coding agent, MCP already wired | — | Yes — prefer structured tools | — | — |
| Linux laptop daily driver | — | — | Yes — computer use not on Linux | — |
| Client machine with payroll / banking UI visible | Only demo data / throwaway | Often yes for live money UIs | — | Never Always allow those apps |
| Org-managed Copilot Business seat, computer use disabled | — | — | Yes — local enable cannot override | — |
Get the 1-page Try desktop control / Skip keep API-MCP-CLI / Wait / Stay approvals-tight chooser
Optional printable of this free guide. Soft link until checkout. Not a “paid summary.” Not a guarantee of clients, savings, or income.
This week’s action — one non-secret GUI workflow
On a non-secret throwaway workflow or demo data, enable computer use: /computer on in Copilot CLI, or Settings → Computer Use → Enable in the Copilot app (/computer show to confirm status; /computer off to disable). On macOS, finish Accessibility and Screen Recording first. Run one constrained prompt in the how-to shape — summarize status, do not change values, do not submit forms. Compare minutes of babysitting and any mis-clicks or approval friction against the structured-tool alternative. Fill one sheet row: Try / Skip / Wait / Stay-tight.
Do not Always-allow banking, payroll, or admin apps. If MCP, CLI, filesystem, or a browser tool already ships the job, skip computer use — do not panic-enable because a Changelog shipped. Do not change a production client GUI mid-week on a public-preview post alone.
Sources: Changelog (1 Oct 2026), About computer use, CLI how-to, App how-to, plans — re-check preview status, OS support, Always-allow behavior, and Pro list price at paste time.