GitHub debuts Copilot desktop preview

GitHub on May 14 put the GitHub Copilot app into technical preview, adding a standalone desktop client for what it calls “agent-driven development.” The app runs on macOS, Windows and Linux, according to GitHub’s changelog and documentation. GitHub described it as a native desktop experience that starts from issues, pull requests, prompts or previous sessions, then carries work through review and merge. (github.blog) (docs.github.com) The release shifts Copilot from being mainly an in-editor assistant toward a broader desktop workflow that includes repository context, terminals, browser previews and pull-request handling. (docs.github.com) GitHub said the app is built on Copilot CLI and works with repositories, branches and CI pipelines “out of the box.” Access is available now for Copilot Business and Enterprise users if admins have enabled preview features and Copilot CLI, while Copilot Pro and Pro+ users must join a waitlist. ### What exactly did GitHub ship on May 14? GitHub’s May 14 changelog entry says the Copilot app is a “GitHub-native desktop experience” for starting agentic development from work already in front of a developer. (github.blog) The company said sessions can begin from an issue, pull request, prompt or earlier session, with issue details, repository state, review comments and checks carried into the session. The GitHub Docs page describes the product as a desktop application for agent-driven development that brings “parallel workstreams, GitHub integration, and PR lifecycle management” into one place. GitHub’s public repository for the app says the project is the home for releases and issues, while the application source code lives elsewhere. (docs.github.com) ### How is this different from using Copilot inside an editor or terminal? GitHub Docs say the app is meant to let users direct AI agents across multiple workstreams without switching between terminals, IDEs and browser tabs. The company says the desktop client can browse issues, start sessions from them, create and close pull requests, review pull requests and view CI check results within the same interface. (github.blog) GitHub’s changelog says the app also includes an integrated terminal and browser so users can run commands, open previews and test changes before opening a pull request. That places terminal execution, review and merge steps inside the same desktop workflow rather than confining Copilot to a single editor session. (docs.github.com) ### How does the app organize agent work? GitHub says each session has its own branch, files, conversation and task state. The documentation adds that isolated sessions use dedicated git worktrees and branches, allowing multiple agents to run at the same time on separate tasks. (docs.github.com) The docs list three session modes: Interactive, where the user collaborates step by step; Plan, where the agent proposes a plan for approval; and Autopilot, which GitHub describes as fully autonomous. GitHub also says users can choose among multiple large language models, adjust reasoning effort per session, and configure MCP servers, skills, extensions and plugins. (github.blog) ### What happens after the code changes are made? GitHub’s May 14 post says the work is not finished until a change is reviewed, tested and ready to merge. The company says users can inspect the plan and diff, leave feedback, validate changes through commands and previews, and then open a pull request from the same session. (github.blog) GitHub also highlighted “Agent Merge,” which it says can address review comments, fix failing checks and merge once preset conditions are met. In the docs, GitHub frames the app as a way to manage the full development lifecycle, not only code generation. (docs.github.com) ### What does this show about GitHub’s broader Copilot push? GitHub’s January 22 post on the Copilot SDK said the same Copilot agentic core can plan, invoke tools, edit files and run commands, and that the SDK exposes the execution loop behind Copilot CLI. That earlier post also said building agentic workflows requires handling permissions, safety boundaries and failure modes. (github.blog) The desktop app uses that same Copilot CLI foundation, according to GitHub Docs and the app repository README. Taken together, GitHub’s recent releases show the company extending Copilot from editor assistance into a wider tool-using runtime that spans local files, commands and GitHub-native review flows; that last point is an inference from GitHub’s product descriptions across the SDK, CLI-based app architecture and May 14 launch materials. (github.blog) ### Where can users get it next? GitHub’s documentation says the app can be installed on macOS, Windows or Linux once a user has access. Business and Enterprise customers can download it from the GitHub Copilot app repository if their administrators have enabled preview features and Copilot CLI, while Pro and Pro+ subscribers can request access through GitHub’s waitlist page as the technical preview expands. (github.blog) (docs.github.com)