GitHub’s advice for its new Copilot feature is to try something else first

6.8 relevance

GitHub's Copilot computer use feature with practical advice on when not to use it, directly relevant to developer experience.

DevTools thenewstack.io

Answer the board on AI readiness

Arrive with evidence, not opinion. See how your foundation benchmarks against your peers, get a clear read, and leave with a ranked place to start.

Why It Matters

For a Solutions Architect building agent orchestration pipelines, this feature extends Copilot to legacy GUI-only apps, but GitHub's cautious guidance to prefer structured tools reinforces the need for reliable, predictable automation over brittle screen-scraping approaches.

Key Takeaways

Evaluate computer use only for legacy GUI apps without API/CLI, and enforce enterprise policies via managed-settings.json to control permission overrides and mitigate security risks.

GitHub’s advice for its new Copilot feature is to try something else first

Summary

GitHub launched computer use in public preview for Copilot CLI and desktop app, letting agents operate GUI apps on macOS/Windows via the OS accessibility tree and screenshots. The company recommends using direct tools (APIs, MCP servers, terminal) over desktop interaction, contrasting with OpenAI Codex and Anthropic Claude Code which already offer similar capabilities. Enterprise policies via managed-settings.json can override local preferences, and the feature has known limitations like action repetition and sensitive data exposure.

Author

Amanda Caswell