Official repository, README, release metadata, and release assets checked on 3 October 2026. No candidate package was downloaded, installed, or run.
A Git client can be a window onto one repository, or a place to follow work across the repository, its host, and the tools acting on it. GitDesktop is pitching the second shape.
The public README describes a Windows, macOS, and Linux application for local Git, pull requests, issues, CI, coding agents, optional AI, and MCP. A v0.13.2 release appeared on 2 October. Those are verified publication facts and upstream product claims; they are not Toolglass test results.
The repository is only the beginning
The README describes an integrated workflow across GitHub, GitLab, and Bitbucket, with Jira in one path. It also lists local pull requests, GitHub Actions, issue work, project boards, branch and history tools, and recovery features. The list is ambitious enough that a feature count would tell us very little.
What matters is whether the state remains understandable as work moves from a local change to a review, a failed check, or a merge conflict. Toolglass has not exercised any of those paths.
The agent boundary is the interesting claim
GitDesktop says its MCP server is read-only by default and describes separate opt-in flags for local writes, remote forge writes, Git mutations, and destructive operations. It also says coding agents can work in isolated worktrees or containers, with their edits visible to the user.
That is a clear design promise, not proof of enforcement. It gives the next pass a useful target: try the read-only path, then check that each write remains unavailable until its specific switch is enabled.
The Windows entry point exists
The latest stable GitHub release we found, v0.13.2, includes a Windows x64 setup executable and MSI. The README says system git is required; GitHub CLI is needed for GitHub pull-request and Actions features, while the other forge and AI integrations have their own optional requirements.
GitHub lists SHA-256 digests for the installers, but Toolglass has not downloaded either file to compare those digests. The README describes signed updater packages; that does not establish the Windows installer’s Authenticode status.
Feature, privacy, signature, and platform statements are attributed to upstream documentation. Release asset SHA-256 values came from GitHub API metadata and were not independently recomputed. Toolglass has no runtime, performance, reliability, or security evidence for this candidate.
Sources & evidence
Project repository and README ↗
Release history ↗
Public material checked 3 October 2026. Version labels are the latest stable release returned at that check, where available. Platform descriptions are upstream claims, not Toolglass acceptance tests.
KEEPING THE DESK OPEN
Toolglass is a small independent publication. If you would like to help keep the testing bench running, see the current support options.
Support Toolglass ↗