GitHub has shipped version 3.6.0 of its Desktop client, landing on Windows and macOS on June 26, 2026, and packing two headlining upgrades: long-awaited Git worktree management and a deep expansion of GitHub Copilot into the everyday commit-and-merge workflow.
For the uninitiated, git worktree lets developers check out multiple branches from the same repository into separate working directories, sidestepping the constant stashing and branch-switching that can fracture focus. Picture simultaneously fixing a critical production bug on main while building the next feature on feat/new-dashboard—no clone duplication, no dependency collisions. GitHub Desktop 3.6 wraps this power in a point-and-click interface. A new \"Worktrees\" pane inside the repository view lets users create a worktree from any branch, name it, pick a local path, and open it in a fresh Desktop window, file manager, or external editor. Switching between worktrees is as simple as double-clicking an entry, and the main window keeps a live count of active worktrees so you never lose track. For Windows users who routinely spin up Visual Studio or VS Code alongside multiple terminals, this means less context shifting and fewer accidental file overwrites.
While worktrees tackle the mechanics of parallel development, the other tentpole feature aims squarely at the cognitive load of writing good commits and merging cleanly. GitHub Copilot, already present in Desktop for code suggestions, now extends into three new areas inside version 3.6:
- AI-generated commit messages: Stage a batch of changes and Copilot examines the diff to propose a concise, descriptive commit title and a bullet-point body. The suggestion appears directly above the commit input field; you can accept, edit, or reject it with a single click. A small sparkle icon next to the commit button indicates the feature is active, and a settings toggle lets you turn it off if you prefer a human touch.
- Merge‑conflict assistance: When a pull, merge, or rebase halts with conflicts, the built‑in conflict resolver now places a \"Resolve with Copilot\" button next to each conflicted file. Clicking it opens a split‑view showing the conflict markers alongside a Copilot‑recommended resolution that respects the intent of both sides. You can accept the suggestion wholesale, tweak it inline, or dismiss it. The feature works with both Git’s standard conflict markers and the custom markers used by editors like VS Code, making it a practical addition for Windows‑centric workflows where VS Code is the default editor.
- Model selection and bring‑your‑own capability: A new Copilot settings pane exposes a dropdown of supported language models. At launch, the list includes GitHub’s default Copilot model, several OpenAI models (GPT‑4o mini, GPT‑4o, and a lightweight on‑device option for offline commit messages), and a slot marked \"Custom.\" The \"Custom\" entry signals the most enterprise‑friendly part of the update: the ability to bring your own Copilot subscription key or even point Desktop at a different AI provider. For organizations with data‑residency requirements or procurement‑approved model suites, this means Copilot features can run against their own licensed models rather than drawing from the public Copilot service. In a brief hands‑on, Windows power users reported that the integration respects existing proxy and certificate settings, a critical detail for corporate environments.
Together, the worktree and Copilot additions turn GitHub Desktop into a more autonomous productivity hub. Developers no longer need to context‑switch to a terminal to manage multiple branches, nor do they have to leave Desktop to get smart commit suggestions or merge aid.
Performance and Windows‑specific refinements
The 3.6 release isn’t all headline features. Under the hood, the app’s Electron shell has been bumped to version 33, bringing a faster JavaScript engine and smoother rendering on Windows 11 with high‑DPI displays. Battery impact on laptops sees a modest dip thanks to more aggressive background throttling when the app is minimized. Windows‑on‑Arm users get a long‑overdue native ARM64 build, trimming launch times by roughly 40% on Surface Pro X and Snapdragon‑powered ThinkPads. Touchscreen interaction—particularly scrolling in the diff view and tapping the new worktree buttons—feels snappier, addressing a long‑standing gripe from tablet‑mode warriors.
How worktrees change the daily flow
Ask any developer who has juggled multiple feature branches, and they’ll recite a litany of tiny frustrations: stash a half‑written change, switch branches, lose the mental warm‑up, switch back, pop the stash, hope nothing conflicts. Worktrees dissolve that dance. In Desktop 3.6, you could:
- Keep your long‑running
feature/auth‑overhaulopen in one window while a QA‑flagged hotfix sits in a second window. - Run two different versions of a debugger simultaneously.
- Experiment with a risky refactor in one directory while the stable build stays untouched in another.
Because each worktree shares the underlying repository’s object database, disk usage is minimal compared to cloning the repo afresh. GitHub Desktop surfaces this by showing the total additional disk space consumed by all worktrees, so you never end up with a bloated drive.
Copilot in the trenches
An early‑access ring of Windows Insiders who received the build a week before the public release shared mixed‑but‑improving sentiment on the AI features. Commit‑message generation “nails the imperative mood most of the time,” said one tester on a private Redmond channel, “but it occasionally gets too chatty for reverts, dropping a whole essay when ‘Revert commit abc123’ would do.” A quick retry button—a refresh icon next to the suggestion—usually tightens the prose. The merge‑conflict assistant won particular praise for its handling of CSS and JSON conflicts, where both sides might add different keys. Rather than blindly concatenate, Copilot often identifies the structural intention and produces a valid merged output.
The model selector drew interest for an unadvertised reason: offline commit messages. When a laptop loses connectivity, the lightweight on‑device model (likely a compressed 1‑3‑billion‑parameter transformer) still churns out suggestions, albeit with slightly less flair. For commuters and field engineers on Windows laptops, that’s a concrete reliability win.
Enterprise implications
The bring‑your‑own‑model slot isn’t just about flexibility; it’s a compliance bridge. Financial‑service developers bound by FedRAMP or SOC2 can point Desktop at a private, audited Copilot instance running on Azure in their tenant. GitHub confirmed that no telemetry from custom‑model requests leaves the user’s configured endpoint, eliminating the data‑flow concerns that kept Copilot off many whitelists. Windows‑domain administrators can push the custom endpoint via Group Policy, locking the setting across the organization.
Furthermore, Desktop 3.6 introduces a new menu under “Options → Integrations” that visually summarizes which Copilot features are active, which model is in use, and how many tokens have been consumed in the current session. For enterprises scrutinizing AI spend, this mini‑dashboard is a small but meaningful nod to transparency.
The road to 3.6
The worktree feature has been the most‑upvoted item on the Desktop roadmap since mid‑2025, accumulating over 3,000 thumbs‑up reactions on the official feedback board. Its inclusion in 3.6 marks the culmination of a year‑long collaboration between the Desktop team, open‑source contributors, and the engineers behind libgit2—the library that powers Git operations under Desktop’s hood. Copilot expansion, meanwhile, tracks a broader GitHub strategy: after embedding AI into pull requests with Copilot for PRs in 2025, the natural next stop was the commit workflow. By owning both the editor (via VS Code) and the version‑control GUI, Microsoft can now offer an AI‑assisted path from first keystroke to merged code without ever leaving its ecosystem.
Community reaction and early kinks
While no major regressions have been flagged in the public Windows user community so far, a handful of early adopters on the GitHub Community Discussions board noted two quirks:
- Worktree‑aware stash handling: If you stash changes in one worktree, those stashes are visible from other worktrees of the same repository. This is correct Git behavior—the stash stack is ref‑based and shared—but it can surprise users expecting worktree‑isolated stashes. Desktop’s UI now adds a small badge that reads “Shared” on the Stash tab when multiple worktrees exist, aiming to reduce confusion.
- Copilot merge resolution and binary files: Merging conflicts in images or other binaries triggers a graceful fallback that says “Copilot cannot resolve binary conflicts,” with a link to open the external merge tool. Some users expected AI‑powered binary diff visualization, but GitHub has acknowledged the limitation and hinted at a future update using an on‑device vision model.
Neither issue is flagged as blocking, and the Desktop team has already merged a patch for the stash‑visibility UX into the 3.6.1 milestone.
A new default for Windows developers?
GitHub Desktop has long been the recommended GUI for those onboarding to Git, but seasoned developers often outgrew it and switched to terminal‑centric tools like GitKraken or Fork. With worktrees, Desktop 3.6 re‑captures that advanced audience. The ability to manage complex branch topologies without touching the command line, paired with an AI copilot that learns the project’s style over successive commits, positions Desktop as a genuine power tool rather than a training wheel. For Windows developers—especially those working in .NET, Azure, and C++ shops where multi‑branch workflows are the norm—the 3.6 release feels less like an incremental update and more like a milestone.
Download GitHub Desktop 3.6.0 from the official release page. Existing installations will receive an automatic update prompt over the coming days. The team has promised a follow‑up blog post detailing the model‑selection internals and on‑device AI packaging, expected in late June 2026.