Generated by Rank Math SEO, this is an llms.txt file designed to help LLMs better understand and index this website.

# GitKraken: Legendary Git GUI client for Windows, Mac & Linux

## Sitemaps
[XML Sitemap](https://gitkraken.com/sitemap_index.xml): Includes all crawlable and indexable pages.

## Posts
- [Keif Schematic](https://gitkraken.com/keif-gallery/schematic-keif)
- [Keif, the Kraken](https://gitkraken.com/keif-gallery/keif-the-kraken)
- [Why I’m excited to join GitKraken](https://gitkraken.com/blog/why-im-excited-to-join-gitkraken): I wanted you to hear directly from me that I’ve joined GitKraken as CEO. I’m honored to succeed Matt Johnston, who has led the company through five years of significant growth and scale.
- [What to Know About AI Code-to-Merge Platforms](https://gitkraken.com/blog/what-to-know-about-ai-code-to-merge-platforms): AI coding agents can generate pull requests at a pace your team has never seen. The bottleneck has shifted from writing code to everything that follows: reviewing, iterating, and merging. AI code-to-merge platforms are the category of tools built to manage that entire lifecycle, from the moment an agent starts working to the moment code lands in your main branch.
- [Can You Prove Your AI Agents Are Paying Off? Most Developers Can’t](https://gitkraken.com/blog/can-you-prove-your-ai-agents-are-paying-off-most-developers-cant): We put a blunt question to developers on a recent live webinar: right now, could you actually prove AI agents are paying off for you or your team? Only 24% said yes. The other 76% were guessing, unsure, or already suspicious that agents are costing more than they're saving.
- [8 Key Gaps in Code Review Collaboration Platforms](https://gitkraken.com/blog/8-key-gaps-in-code-review-collaboration-platforms): Your code review collaboration platform probably does a decent job showing diffs. But for distributed teams, the toughest problems rarely live inside the diff itself. They hide in handoff gaps, missing context, and review bottlenecks that no feature checklist warns you about.
- [Kepler Tutorials: Every Video You Need to Get Started](https://gitkraken.com/blog/kepler-tutorials-every-video-you-need-to-get-started): Running one coding agent is manageable. Running four of them across three repos, each at a different stage, each waiting on something different from you, is where most developers lose the thread. That's the problem Kepler is built to solve, and it's also why we put together a full tutorial series instead of a single walkthrough. Parallel agent work has more moving parts than a five-minute demo can cover.
- [What Are Stealth Models?](https://gitkraken.com/blog/what-are-stealth-models): The recent mystery around Ox Alpha last week and the week before was a fun slice of what makes social media fun. The hunt for the model provider and how people did that discovery should be studied. But, this post is more about stealth models in general. You might be wondering what the phrase "stealth model" even means and if you already know, you might still be curious about why companies release stealth models.
- [Why We Stopped Reading Agent Logs Like a Waterfall](https://gitkraken.com/blog/why-we-stopped-reading-agent-logs-like-a-waterfall): Giordano "Gyo" Piazza, GitKraken's Director of Engineering, has spent the past month heads down on the next version of Kepler. When he got on a call to talk through it, he skipped the changelog and went straight to the part he actually wanted to talk about: how agents show their work.
- [Don’t Sleep on Perplexity](https://gitkraken.com/blog/dont-sleep-on-perplexity): Perplexity was a big name a few years ago. But, we haven't heard much out of them lately. There are plenty of posts on social media criticizing Perplexity to that effect. One thing that the posts miss is that Perplexity is still the king of AI search. Google is giving it a run for its money with the AI previews on Google search, but Perplexity still wins out in several measurable ways.
- [6 Things to Know Before Choosing an SEI Platform in 2026](https://gitkraken.com/blog/6-things-to-know-before-choosing-an-sei-platform-in-2026): Choosing a software engineering intelligence platform is one of those decisions that gets more complicated the longer you wait. The category has grown rapidly, and every vendor claims to track the metrics that matter.
- [What to Look for in Code Review Platforms](https://gitkraken.com/blog/what-to-look-for-in-code-review-platforms): Your code review tool does more than display diffs. It shapes how your team shares knowledge, catches bugs, and ships software. With AI-generated code accelerating PR volume, choosing the right code review platform is a decision that directly affects your team's velocity.
- [Inside the Live Launch: What We Showed for GitKraken Insights for Developers and Kepler](https://gitkraken.com/blog/live-launch-gitkraken-insights-for-developers): We hosted a live launch preview, "Level Up Your Agentic Workflow," to introduce two things at once: GitKraken Insights for Developers and Kepler. Jeremy Castile, our VP of Developer Research, opened with research on how teams are actually using AI agents today. If you want the full breakdown of that data, including the adoption numbers and the gap between feeling faster and proving it, we published it separately in State of AI in Engineering 2026: The Proof Gap. This post covers what came after: the live product demos and the questions that came out of them.
- [Kepler: One place to run every agent, from idea to merged](https://gitkraken.com/blog/big-kepler-release): The biggest Kepler update since public preview is live. If you tried Kepler early, here's what changed, and the problem it's built to solve.
- [Everyone Feels Faster. Almost Nobody Can Prove It.](https://gitkraken.com/blog/everyone-feels-faster-almost-nobody-can-prove-it): What 554 developers and engineering leaders told us about AI, agents, and the measurement gap nobody's closing.
- [You Aren’t As Behind As You Think](https://gitkraken.com/blog/you-arent-as-behind-as-you-think): TL;DR: There have been a couple tweets and posts about the AI adoption curve that I found interesting:
- [AI Was Supposed to Mean Working Less. For Some Developers, It’s Doing the Opposite.](https://gitkraken.com/blog/ai-was-supposed-to-mean-working-less-for-some-developers-its-doing-the-opposite): AI coding tools were supposed to mean developers work less. On a recent webinar recorded with LeadDev, senior engineering manager Vernon put words to something a lot of teams are quietly noticing instead: 
- [GitLens 19 Shows You the Whole Stack, Not Just the Next Pull Request](https://gitkraken.com/blog/gitlens-19-shows-you-the-whole-stack-not-just-the-next-pull-request): Splitting one big pull request into five smaller ones doesn't automatically make review faster. It just moves the complexity from the diff to your head, unless something keeps track of the order for you.
- [Kepler and Insights: Built From Opposite Directions](https://gitkraken.com/blog/kepler-and-insights-built-from-opposite-directions): Most companies buy AI tools for developers and hope the impact shows up somewhere. A faster sprint. Fewer escaped bugs. Something. What they don't have is a way to actually see it happening, which means adoption becomes a leap of faith instead of a measured bet.
- [How a Request in Slack Turns Into a GitKraken Feature](https://gitkraken.com/blog/how-a-request-in-slack-turns-into-a-gitkraken-feature): Most companies will tell you they're customer-obsessed. Fewer can point to the actual mechanism. At GitKraken, it isn't a quarterly survey or a roadmap council. It's a Slack channel where developers vent about their Git workflow, and the desktop team is already in there reading it.
- [GitLens 19: The Commit Graph Reimagined for Parallel Development](https://gitkraken.com/blog/gitlens-19-the-commit-graph-reimagined-for-parallel-development): Visualize branches and commits, manage parallel work and agents, and run your entire Git workflow from one view.
- [ACP: The Protocol Powering Kepler](https://gitkraken.com/blog/acp-the-protocol-powering-kepler): The secret sauce that powers Agentic Development Environments (ADEs) like Kepler is a little thing called the Agent Client Protocol (ACP). In this context, Kepler is the Client and harnesses like Claude Code and the Codex CLI are the Agents. We're going to go over some of the details about how it works, how we use it at GitKraken, and how the protocol may be changing for the better.
- [An 80% AI Adoption Rate Is Like an 80% Gym Membership Rate. It Doesn’t Prove Anyone Got Stronger.](https://gitkraken.com/blog/an-80-ai-adoption-rate-is-like-an-80-gym-membership-rate-it-doesnt-prove-anyone-got-stronger): Leadership has stopped asking whether your team is using AI. They're asking what you're delivering with it. That's a harder question, because most of the numbers teams have been reporting, adoption rate, seats activated, prompts run, don't actually answer it.
- [Every AI Agent You Add Leaves Something Behind to Clean Up](https://gitkraken.com/blog/every-ai-agent-you-add-leaves-something-behind-to-clean-up): Adding a second AI agent to a project feels like doubling your output. In practice, it usually means doubling your bookkeeping too. Every agent needs its own worktree so it can work without touching the branch someone else, human or otherwise, is using. Multiply that by five agents across three repos, and the isolation that made parallel work possible starts generating its own kind of work: which worktree goes with which branch, which ones are stale, which upstream nobody remembers creating.
- [Open Models Are Closing the Gap](https://gitkraken.com/blog/open-models-are-closing-the-gap): The frontier models have led the pack for a while now. It seems like the big players of Anthropic and OpenAI keep leapfrogging each other by a couple points in benchmark scores every other month. But, a trend we are starting to see is that open weight models are improving by leaps and bounds. They don't hold the lead and probably won't for a while, but the fact that open models are scaring the leaders is something to think about.
- [Why Kepler Doesn’t Care Which AI Agent You Use](https://gitkraken.com/blog/why-kepler-doesnt-care-which-ai-agent-you-use): Most teams adopting AI agents are making a bet on which one wins. Claude or Codex, Copilot or something newer next quarter. That bet is the wrong one to make. The agent you use will keep changing. The workflow around it is what actually needs to hold up.
- [GitKraken Desktop 12.4: See Every Agent, Approve Every Change](https://gitkraken.com/blog/gitkraken-desktop-12-4-see-every-agent-approve-every-change): GitKraken Desktop 12.4 gives developers running several worktrees and AI agent sessions a single graph to see it all, plus an inline way to approve or deny what each agent wants to do. It ships August 4, 2026, with updates carried forward from 12.1 through 12.4.
- [Straight from Support: AI credits, student plans, and why your Mac fans are so loud](https://gitkraken.com/blog/straight-from-support-ai-credits-student-plans-and-why-your-mac-fans-are-so-loud): Every so often we sit down with someone from our support team and turn their week into a blog post. First up: Roberto Vizcarra, on four things generating tickets lately, AI credits, student plans, integrations, and Mac performance. Here's what changed and what to do about it.
- [Kepler Is in Public Preview: One Task, Every Repo, Every Agent](https://gitkraken.com/blog/kepler-is-in-public-preview-one-task-every-repo-every-agent): A faster car doesn’t get you home faster if the freeway is still jammed. That is the problem most teams run into once they add a second, third, or fourth AI coding agent to the mix. More agents generate more code. They do not automatically generate more finished work, because someone still has to track which agent is waiting on input, which one just opened a pull request, and which one has been quietly stuck for twenty minutes.
- [GitKraken’s Claude Code Plugin Is Live: No CLI Required](https://gitkraken.com/blog/gitkraken-claude-code): If you haven't heard about our MCP server, you should really check it out. It's probably the best way to give your agents access to the power of GitKraken's integrations and features. Our MCP tools also help your agents understand your codebase in a way that we think lowers your token usage and improves their output.
- [GitKraken Code Review: A Different Way to See What a Pull Request Actually Changed](https://gitkraken.com/blog/gitkraken-code-review-a-different-way-to-see-what-a-pull-request-actually-changed): Most PR descriptions leave out the one thing a reviewer actually needs: why the change was made. And AI review bots that live natively inside GitHub tend to solve that with noise instead, dropping comments a reviewer then has to sort through to find the two that matter.
- [GitLens 18 Turns the Commit Graph Into an Agent Command Center](https://gitkraken.com/blog/gitlens-18-turns-the-commit-graph-into-an-agent-command-center): Five coding agents sounds like leverage right up until a developer is the one keeping track of all five: one fixing a bug, one building a feature, one refactoring, and two waiting on input at the same time. AI did not create that problem. It exposed a workflow problem that was always going to surface once parallel development became normal instead of occasional.
- [Do Gemini Models Deserve the Hate?](https://gitkraken.com/blog/gemini-models-are-misunderstood): Recently, Google released a couple new Gemini models. They were Gemini 3.6 Flash, 3.5 Flash Lite, and 3.5 Flash Cyber. Many people on the internet roasted Gemini Flash and Flash Lite for their less-than-frontier performance. This makes sense when you consider that OpenAI and Anthropic have been sparring back and forth for first place for quite a while but Gemini almost never gets that first place position. After all, this is Google we are talking about. Many people assume they have been scraping the world's internet for decades and should have a lead based on that. They even created the Transformer before OpenAI realized its value. So, it has become a bit of a meme to roast Google's models when they release.
- [GitKraken Desktop: Go Deep on One Repo, With an Agent Riding Along](https://gitkraken.com/blog/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.
- [Why We Built Kepler: One Engineer’s Frustration With Fifteen Open Terminals](https://gitkraken.com/blog/why-we-built-kepler-one-engineers-frustration-with-fifteen-open-terminals): We didn't set out to build a new category of product. We set out to stop juggling.
- [GitLens 18.2: AI-Powered Merge Conflict Resolution for VS Code](https://gitkraken.com/blog/gitlens-18-2-ai-powered-merge-conflict-resolution-for-vs-code): Merge conflicts rarely make it into a sprint retrospective, but they should. They’re one of the most reliable ways to lose an hour of flow without anyone noticing it’s gone. Every developer expects them eventually, but almost nobody questions the workflow around resolving them.
- [Introducing GitBench](https://gitkraken.com/blog/introducing-gitbench): TL;DR: You can see the results of GitBench here https://gitbench.gitkraken.com
- [GitKraken: The Code Flow Company](https://gitkraken.com/blog/gitkraken-the-ai-code-flow-company): From plan to main.
- [](https://gitkraken.com/answers/7-sei-platforms-for-ai-impact-and-git-bottlenecks): GitKraken Insights gives engineering leaders visibility into how AI tools affect team productivity, alongside DORA metrics and Git workflow analysis. This guide compares seven SEI platforms that help you prove AI impact and find bottlenecks in your development process.
- [](https://gitkraken.com/answers/how-code-ownership-tracking-speeds-troubleshooting): Git history remains valuable even after someone leaves. The commit messages and PR descriptions they wrote become documentation. GitKraken Insights can help your team track these patterns and spot areas of the codebase that may need additional attention after transitions.
- [](https://gitkraken.com/answers/gitlens-vs-git-graph-pull-request-workflows-in-vs-code): If you're picking a Git extension for VS Code, the choice often comes down to two popular options: GitLens and Git Graph. Both help you visualize commit history and understand code changes, but they take different approaches to pull request workflows and team collaboration.
- [](https://gitkraken.com/answers/the-complete-guide-to-git-merge-conflict-resolution): GitKraken Insights can help you track merge patterns and identify recurring issues. Data-driven improvements are more effective than guesses.
- [](https://gitkraken.com/answers/git-workflow-intelligence-for-mid-sized-teams-in-2026): That's changing. Engineering intelligence platforms now connect directly to Git providers, transforming repository activity into metrics that reveal delivery patterns, surface bottlenecks, and show whether your process changes actually improve outcomes. GitKraken Insights gives mid-sized teams the ability to track DORA metrics, pull request flow, and AI coding tool impact without the overhead of building measurement infrastructure from scratch.
- [](https://gitkraken.com/answers/how-to-build-an-engineering-roi-dashboard-in-7-steps): GitKraken Insights automatically tracks DORA metrics, code quality indicators, and AI tool impact across your repositories. The platform connects to GitHub, GitLab, Bitbucket, and Azure DevOps—pulling data from wherever your code lives.
- [](https://gitkraken.com/answers/how-to-justify-engineering-investments-with-data): GitKraken Insights tracks all four DORA metrics with the trend context that matters for decision-making. When lead time spikes from 1.4 to 6.7 days, trend lines show whether it's a temporary issue or an emerging pattern requiring intervention.
- [](https://gitkraken.com/answers/7-engineering-analytics-tools-for-release-bottlenecks-in-2026): Your team writes code faster than ever. AI assistants generate pull requests in hours instead of days. Yet release dates keep slipping and review queues grow longer each sprint. GitKraken Insights gives you visibility into where work actually gets stuck—connecting code velocity to delivery outcomes so you can find and fix bottlenecks before they derail your roadmap.

## Pages
- [State of AI](https://gitkraken.com/reports/state-of-ai): Everyone feels faster. Almost nobody can prove it.
- [Kepler Download Linux rpm ARM](https://gitkraken.com/kepler/download/linux-rpm-arm64): Download didn't start? Try downloading again
- [Kepler Download Linux rpm](https://gitkraken.com/kepler/download/linux-rpm-64): Download didn't start? Try downloading again
- [Kepler Download Linux deb ARM](https://gitkraken.com/kepler/download/linux-deb-arm64): Download didn't start? Try downloading again
- [Kepler Download Linux deb](https://gitkraken.com/kepler/download/linux-deb-64): Download didn't start? Try downloading again
- [Kepler Download Linux AppImage ARM](https://gitkraken.com/kepler/download/linux-appimage-arm): Download didn't start? Try downloading again
- [Kepler Download Linux AppImage](https://gitkraken.com/kepler/download/linux-appimage): Download didn't start? Try downloading again
- [Kepler Download Windows ARM64](https://gitkraken.com/kepler/download/windows-arm64): Download didn't start? Try downloading again
- [Kepler Download Windows 64](https://gitkraken.com/kepler/download/windows-64): Download didn't start? Try downloading again
- [Kepler Download macOS 64](https://gitkraken.com/kepler/download/macos-64): Download didn't start? Try downloading again
- [kepler download macOS arm](https://gitkraken.com/kepler/download/macos-arm): Download didn't start? Try downloading again
- [GitKraken Client Try Free – C](https://gitkraken.com/git-client/try-free-c): GitKraken works natively with your repos, issues, IDEs, agents and more, so you can reduce context switching and focus on building.
- [Agent Management](https://gitkraken.com/features/agent-management): GitKraken Agent Management is built into GitKraken Desktop, GitLens, and Kepler. Launch and monitor AI coding agents, and run work in parallel across your private repos, without leaving your normal tools.
- [Index – 2026](https://gitkraken.com/): Kepler by GitKraken ADE gives developers a purpose-built environment for collaborating with AI on real software work, without losing context, oversight, or momentum.
- [Code Reviews for Git Workflows](https://gitkraken.com/features/code-review): GitKraken Code Review helps teams understand pull requests faster by reducing noise, highlighting meaningful logic changes, and building context with AI-assisted workflows, all without leaving existing Git provider workflows.
- [Kepler -lp](https://gitkraken.com/lp/project-kepler): Project Kepler
- [LeadDev – 2026](https://gitkraken.com/insights-leaddev-2026):   GITKRAKEN INSIGHTS

## Listing Items/Components
- [Event Card](https://gitkraken.com/?jet-engine=events): Event Card
- [Logos](https://gitkraken.com/?jet-engine=logos)