Get 40% Off GitKraken Pro

Git Blog

Releasing the Power of Git

GitKraken Desktop: Go Deep on One Repo, With an Agent Riding Along

Before agents were part of the picture, GitKraken Desktop had one job: make Git make sense. Visualize the commit graph, show branches and remotes clearly, and let a developer feel confident hitting merge. That job has not changed. What changed in GitKraken Desktop 12 is what sits on top of it.

What are agent sessions in GitKraken Desktop?

Agent sessions, introduced in GitKraken Desktop 12, let a developer start a coding agent directly from the left panel and work with it inside the same client that already shows the repo’s history. It supports Claude Code, Codex, Gemini, OpenCode, Copilot, Augment, and others, so the choice of agent is not locked to the tool.

Built for going deep on one repo

GitKraken Desktop is the tool for going deep on a single repository with an agent. That is the distinction from Kepler, which is built for going wide across many repositories at once. A developer working through one focused task, one branch, one agent, gets everything in GitKraken Desktop: the diff, the graph, and the commit history, in one window.

The moment it gets useful: catching an agent in the act

GitKraken Desktop can detect when an agent working outside the app, in a terminal running Claude Code for example, is actively editing a worktree, and it surfaces a direct shortcut to open that worktree with the live diff already in view. A developer does not have to go looking for what changed. GitKraken Desktop notices and offers it up.

That single detail does the real work of the tool: it turns “trust the agent and hope” into “see exactly what changed, right now, and decide.”

From there, it is the same trusted workflow

Once a change looks right, the path from there is the one developers already know: stage it, commit it, and push it toward a pull request, ready for review. Nothing about verifying and merging code changes because a machine wrote it.

Frequently asked questions

What is the difference between GitKraken Desktop and Kepler? GitKraken Desktop is built to go deep on one repository at a time with an agent. Kepler is built to coordinate agents across many repositories in a single task.

Which AI agents work with GitKraken Desktop? Claude Code, Codex, Gemini, OpenCode, Copilot, Augment, and any agent built on the Agent Client Protocol.

Do I still get the commit graph and branch visualization? Yes. Agent sessions sit on top of the same graph, remotes, and branch view GitKraken Desktop has always provided.

Download GitKraken Desktop at gitkraken.com and start an agent session from the left panel on any repo already cloned locally.

Like this post? Share it!

Read More Articles

Introducing GitBench

TL;DR: You can see the results of GitBench here https://gitbench.gitkraken.com GitBench is our attempt to see how well LLMs handle git-specific tasks. We put together

Read More »
Visual Studio Code is required to install GitLens.

Don’t have Visual Studio Code? Get it now.

Team Collaboration Services

Secure cloud-backed services that span across all products in the DevEx platform to keep your workflows connected across projects, repos, and team members
Launchpad – All your PRs, issues, & tasks in one spot to kick off a focused, unblocked day. Code Suggest – Real code suggestions anywhere in your project, as simple as in Google Docs. Cloud Patches – Speed up PR reviews by enabling early collaboration on work-in-progress. Workspaces – Group & sync repos to simplify multi-repo actions, & get new devs coding faster. DORA Insights – Data-driven code insights to track & improve development velocity. Security & Admin – Easily set up SSO, manage access, & streamline IdP integrations.
winget install gitkraken.cli