GitHub launches Copilot desktop preview
- GitHub said on May 14 it put its new Copilot desktop app into technical preview, adding a standalone client for agent-driven software work. - GitHub said the app starts from issues, pull requests, prompts or past sessions, with Business and Enterprise access rolling out during the week. - GitHub’s docs say Pro and Pro+ users must join a waitlist, while organizations need preview features and Copilot CLI enabled.
GitHub said on May 14 that it had opened a technical preview of a new GitHub Copilot desktop app, giving its coding assistant a standalone client on macOS, Windows and Linux. The company described the software as a GitHub-native desktop experience for “agentic development,” built to let developers start from an issue, pull request, prompt or previous session and carry work through review and merge. GitHub said Copilot Pro and Pro+ subscribers can sign up for early access as the preview expands, while Business and Enterprise customers would get access as availability rolled out through the week. ### What does the desktop app actually do that GitHub’s existing Copilot tools do not? GitHub’s documentation says the app is designed to manage “parallel workstreams, GitHub integration, and PR lifecycle management” in one place. The software includes an inbox for issues and pull requests, sessions grouped by repository, search across repositories and saved workflows that can run on demand or on a schedule, according to the docs. (github.blog) The May 14 changelog says each session gets its own branch, files, conversation and task state. GitHub said users can pause and resume work, review diffs, run commands, open previews, test changes in an integrated terminal and browser, and then open a pull request using the same reviews, checks and merge requirements already attached to the repository. (docs.github.com) ### Who can use it now, and who still has to wait? GitHub’s quickstart page says Business and Enterprise users can use the app if their organization has enabled preview features and Copilot CLI. Those users do not need a waitlist and can download the app directly from the GitHub Copilot app repository, the company says. Copilot Pro and Pro+ users face a narrower path. (github.blog) GitHub says those individual subscribers must join a waitlist and be accepted into the preview before they receive a download link. The changelog separately says Pro and Pro+ subscribers can sign up for early access as the technical preview expands. ### How does this fit with GitHub’s broader push into coding agents? (docs.github.com) GitHub said in February that Claude by Anthropic and OpenAI Codex became available in public preview on GitHub and in Visual Studio Code for Copilot Pro+ and Copilot Enterprise subscribers. In that announcement, GitHub said Agent HQ would let developers run multiple coding agents from different providers inside GitHub and their editor while keeping context, history and review attached to the work. (github.blog) The New Stack reported on May 16 that the new desktop app places GitHub more directly into the desktop-agent field alongside Claude Code and Codex. That publication said the client is built on GitHub Copilot CLI, which reached general availability in February, and brings those agent capabilities into a graphical interface for supervising sessions, repositories and tasks. (github.blog) ### Why is GitHub being selective about access? GitHub said on April 20, in a post updated May 14, that it had paused new sign-ups for Copilot Pro, Pro+ and Student plans and tightened usage limits for individual plans. Joe Binder, a GitHub executive, wrote that “agentic workflows have fundamentally changed Copilot’s compute demands,” with long-running parallel sessions consuming more resources than the original plan structure was built to support. (thenewstack.io) That post said Pro+ plans offer more than five times the limits of Pro, and that GitHub was adjusting model availability and displaying usage limits in VS Code and Copilot CLI. The company said the changes were meant to protect service quality for existing customers. ### Where does GitHub want developers to start using the app? (github.blog) GitHub’s changelog says sessions can begin from “real work” already living in GitHub, including issues, pull requests, prompts and previous sessions. The docs say onboarding prompts users to pick repositories based on recent GitHub activity or a sample project, and later lets them add a local folder, a GitHub repository or any Git URL. (github.blog) The next step is spelled out in GitHub’s own documentation. Business and Enterprise administrators must enable preview features and Copilot CLI in policy settings, while Pro and Pro+ users must join the waitlist and wait for acceptance into the technical preview. (github.blog)