Install and system requirements
GitKraken Desktop runs on Windows 10 or later in 64-bit form, with ARM64 support in preview. It also supports macOS 12 or later and Linux. The Windows installer starts the application without presenting setup options, so installation does not require choosing components or configuring paths.
On first launch, you must sign in to an existing GitKraken account or create one. A new account starts a 14-day trial of Pro and Advanced features. GitKraken Desktop includes what it needs for basic repository work, so a separate Git installation is not required for that use.
After setup, GitKraken Desktop lets you work with local repositories and connect to remote Git hosts. The free Community plan remains available after the trial for local repositories and public cloud-hosted repositories. Private remote repositories and several additional capabilities require a paid plan; when the trial ends, private repository access is locked unless you upgrade.
Working with repositories
The main interface presents repository history as an interactive graph of commits and branches. This gives you a visual way to follow how branches diverge and come together, rather than relying only on a text-based history. You can use drag and drop to perform merges and rebases, and the graph makes branch relationships part of the normal workflow.
For everyday source-control tasks, the client supports committing changes and creating or managing branches, as well as merging and rebasing. Its visual controls are intended to make these operations accessible without requiring command-line Git for basic use. The interface is consistent across Windows, macOS, and Linux.
Merge conflicts and host connections
When a merge produces a conflict, the built-in merge editor shows both sides so you can compare their changes. You can select the result or edit it directly, then resolve the conflict within the application. This keeps conflict review connected to the merge workflow instead of requiring a separate editor for that task.
GitKraken Desktop can connect to GitHub, GitLab, Bitbucket, and Azure DevOps for cloning repositories and working with pull requests. The free plan’s remote-repository access is limited to public repositories, so connecting to a supported host does not make private repositories available without a paid plan.
Worktrees, agents, and plan boundaries
The application can manage Git worktrees, which let you maintain separate working directories associated with a repository. It can also run coding agents such as Copilot CLI or Claude Code in separate worktrees, keeping those agent sessions apart from other work in progress.
Some capabilities are restricted to paid plans. These include private remote repositories, multiple profiles, cloud issue tracker integrations, Launchpad, and GitKraken AI. The free Community plan is therefore most suitable when repository work is local or uses public hosted projects; teams relying on private remote repositories need to account for the paid-plan requirement after the trial.
Practical fit
GitKraken Desktop is a closed-source Git client made by Axosoft, LLC (GitKraken). Its defining workflow centers on the commit graph and built-in conflict editor, with host connections and worktree management providing additional ways to organize repository work. The application is Electron-based and can feel fairly heavy, and using it requires a GitKraken account.
For developers who prefer to understand branches visually and primarily work with local or public repositories, the Community plan provides a continuing free option. If private repositories are central to your work, plan access around the paid features rather than assuming the trial’s private-repository support will continue afterward.
