# GitHub Desktop 3.6 brings worktrees into the desktop client > The desktop release lets developers manage parallel working trees and deepens Copilot support for commit messages and conflict resolution. Canonical URL: https://www.devobs.io/news/news-github-desktop-3-6-worktrees/ By: Arjun Shah Published: 2026-09-06T11:58:54.642Z Updated: 2026-09-06T11:58:54.642Z Event date: 2026-06-26 Section: Developer tools GitHub released Desktop 3.6 on June 26 with user-interface support for Git worktrees and additional Copilot assistance. The [release announcement](https://github.blog/changelog/2026-06-26-github-desktop-3-6-worktrees-and-deeper-copilot-integration/) highlights parallel working directories, commit-message authoring, and help during merge-conflict resolution. ## Parallel branches without repeated clones A worktree gives one repository multiple checked-out branches in separate directories. That is useful when a developer must review a pull request while a feature branch remains open, compare two builds, or hand an isolated directory to an automation tool. Bringing the operation into GitHub Desktop makes the feature accessible without requiring developers to remember the underlying `git worktree` commands. Worktrees still share repository metadata and object storage. They are not independent clones or security boundaries, and Git prevents the same branch from being checked out in two worktrees. Tools that assume the `.git` path is always a directory may also need testing because linked worktrees commonly use a pointer file. ## Update team habits with the client Before adopting worktrees widely, test editors, language servers, build caches, container mounts, and scripts that derive paths from the repository root. Give each worktree its own dependency or output directory when concurrent builds would otherwise overwrite shared state. Establish a simple cleanup practice so old branches do not leave confusing directories behind. Treat Copilot-generated commit messages and conflict resolutions as proposals. A conflict can be syntactically resolved while still combining incompatible behavior, so run the same tests and review that a manual resolution requires. Teams that standardize commit formats should check generated messages against those rules. Desktop 3.6 reduces interface friction, but the correctness of parallel changes still depends on clear branch ownership and verification. ## Source references -