|
By Chris Griffing
I built GitBench because I was curious about how well models did git things. It turns out that it was a good idea because some models will surprise you. Some of the frontier models were remarkably bad and some cheap open models punched above their weight class. But, as they say, “the times they are a changin’”. Before I go too deep into the latest results, you may want to read up on GitBench and what it is and why I built it in the previous blog post.
|
By Jade Nangah
Five worktrees for five agents sounds like organization. In practice, it’s five contexts to keep straight, five places history could live, five spots for a WIP that gets left behind or diffed against the wrong branch. GitLens 19.2’s fix isn’t a second graph. It’s making the one graph you already trust point wherever the work actually is.
|
By Chris Griffing
There is no doubt that LLMs have changed how we work as developers. You can go back just a year from today and I would have had a very different opinion. But, things have changed significantly. Complex work usually involves just prompting an agent for it. You still need taste and opinions to steer it the right way. With that in mind, it’s easy to se that the future of the IDE might be uncertain.
|
By Jade Nangah
Every new AI coding agent comes with the same pitch: write code faster. For most devs, that part already checks out. Codex writes a function in seconds. Claude Code refactors a file mid-meeting. Copilot fills in a test before you finish describing it. None of that touches the problem that shows up an hour later: five agents running across three repositories, each with its own diff, and no single place to see what’s stuck, what’s done, and what’s actually safe to ship.
|
By Jade Nangah
Finding the right pull request review tool can mean the difference between a team that ships confidently and one that drowns in open PRs. When review workflows are scattered across tabs, comment threads, and standalone dashboards, code quality and velocity both take a hit. GitKraken gives you a unified code review experience that connects your IDE, desktop client, and browser so reviews happen where you already work.
|
By Chris Griffing
One of the features I have been wanting in Kepler for a long time was the ability to use Pi as my agent when spinning up tasks. Pi is such a minimal harness that it doesn’t prompt for approval for every little thing and it’s system prompt let’s the model just be itself. That minimalism comes at a cost, though. Pi doesn’t have ACP support out of the box, so that means we haven’t been able to officially support it in Kepler, yet.
|
By Jade Nangah
Every so often we sit down with someone from our support team and turn their week into a blog post. This time, Roberto walks us through four things generating tickets right now: an upcoming Microsoft authentication change, how AI credit pools actually work, multi-account support in Kepler, and a one-line fix for laggy GitKraken on Linux or WSL. Here’s what’s changing and what to do about it.
|
By Chris Griffing
Internal hackathons are a powerful way to let your teams explore ideas and work together on something fun besides the same old stuff for work. Maybe they want to build something brand new, maybe they want to knock out things that are on the backlog that never get prioritized, or maybe they want to work on something fun but completely unrelated to work.
|
By Jade Nangah
Running AI coding agents in parallel across repositories is no longer experimental. It’s how high-performing engineering teams ship faster. But the tools you pick to orchestrate those agents can either multiply your output or introduce new bottlenecks. GitKraken gives your team a purpose-built surface for AI coding agent orchestration through Kepler, its agent-agnostic development environment. Before you commit to any orchestration tool, though, you need to ask the right questions.
|
By Jade Nangah
Pull request queues keep growing, reviewers lose context between rounds of feedback, and merges stall for days. If your team’s code review process has become a bottleneck instead of a quality gate, the tooling around it may be the real issue. GitKraken gives you a unified code review workspace that cuts through noise and surfaces meaningful changes so reviewers focus on what matters.
|
By GitKraken
Our Director of Engineering on why watching an agent's raw text log doesn't work, and why Kepler now shows you a graph instead.
|
By GitKraken
AI feels faster. Make sure it is. GitKraken Insights shows engineering leaders the real cost, output, and ROI of their AI investment, per tool, per team, per developer. Then it gives every developer their own data and coaching to get more from it. 84% of developers say they feel more productive with AI. Only about one in five can actually measure the impact.* With GitKraken Insights, you can: We run on it ourselves: GitKraken's own engineering org reached 2.53x output in six months.
|
By GitKraken
In Kepler ADE by GitKraken, you can connect and use whichever AI coding agents fit your workflow. This video shows how to configure agents, set defaults, manage multiple accounts, and run parallel sessions.
|
By GitKraken
Most AI model benchmarks measure general coding ability or reasoning. GitBench, built by GitKraken developer advocate Chris Griffing, measures something narrower and more practical: how well a given AI model handles specific Git tasks, starting with commit squashing, identifying which commits in a messy history should be combined into one clean commit.
|
By GitKraken
What if you could counterspell an agent action? GitKraken Desktop 12.4 pulls the whole AI agent workflow into one place, so you stay in the flow. Back in 12.0 we shipped Agent Sessions, where you kick off AI coding agents right inside the context of your repo. GitKraken 12.4 builds on that. What's new in 12.4: This release is not about handing more of your work to agents. It's about seeing everything they do, and deciding what actually changes.
|
By GitKraken
Kepler is GitKraken's new agentic development environment (ADE), and it's now in public preview for Windows, Mac, and Linux. If GitKraken Desktop is built to go deep on one repository, Kepler is built to go wide: one task, multiple repositories, multiple AI agents, tracked in a single place instead of a dozen open terminals.
|
By GitKraken
GitLens 19 is here, with a reimagined Commit Graph built to be your workbench for modern parallel development. See what’s happening across branches, worktrees, and supported coding agent sessions, then move the work forward without constantly jumping between views and tools.
|
By GitKraken
Code Flow is what we call the shift happening across every engineering team right now: AI can generate code faster than ever, but that doesn't mean it ships any faster. In this clip from our Code Flow Live stream, our team unpack why adding AI coding agents to a team is a lot like adding lanes to a highway that's already jammed. More lanes, more cars, same traffic.
|
By GitKraken
Everyone's betting on which AI agent wins. Wrong bet. The agent you use will keep changing. The workflow around it is what needs to hold up. That's why Kepler connects to any agent, Claude, Codex, Copilot, instead of locking you into one.
|
By GitKraken
What if you could counterspell an agent action? GitKraken Desktop 12.4 pulls the whole AI agent workflow into one place, so you stay in the flow. Back in 12.0 we shipped Agent Sessions, where you kick off AI coding agents right inside the context of your repo. GitKraken 12.4 builds on that. What's new in 12.4: This release is not about handing more of your work to agents. It's about seeing everything they do, and deciding what actually changes.
- September 2026 (16)
- August 2026 (28)
- July 2026 (14)
- June 2026 (7)
- May 2026 (20)
- April 2026 (12)
- March 2026 (13)
- February 2026 (10)
- January 2026 (11)
- December 2025 (2)
- November 2025 (11)
- October 2025 (15)
- September 2025 (10)
- August 2025 (10)
- July 2025 (20)
- June 2025 (8)
- May 2025 (5)
- April 2025 (3)
- March 2025 (9)
- February 2025 (6)
- January 2025 (14)
- December 2024 (6)
- November 2024 (18)
- October 2024 (10)
- September 2024 (19)
- August 2024 (6)
- July 2024 (27)
- June 2024 (27)
- May 2024 (26)
- April 2024 (29)
- March 2024 (28)
- February 2024 (27)
- January 2024 (16)
- December 2023 (29)
- November 2023 (22)
- October 2023 (8)
- September 2023 (9)
- August 2023 (7)
- July 2023 (2)
- June 2023 (2)
- May 2023 (4)
- April 2023 (5)
- March 2023 (5)
- February 2023 (6)
- January 2023 (10)
- December 2022 (3)
- November 2022 (2)
- October 2022 (3)
- September 2022 (5)
- August 2022 (3)
- July 2022 (4)
- June 2022 (5)
- May 2022 (5)
- April 2022 (6)
- March 2022 (4)
- February 2022 (4)
- December 2021 (4)
- November 2021 (15)
- October 2021 (2)
- September 2021 (6)
- August 2021 (1)
- July 2021 (4)
- June 2021 (1)
- May 2021 (2)
- January 2021 (3)
- November 2020 (2)
- October 2020 (3)
- September 2020 (2)
- August 2020 (3)
- July 2020 (3)
- June 2020 (3)
- May 2020 (2)
- April 2020 (3)
- March 2020 (4)
- February 2020 (5)
- January 2020 (5)
- December 2019 (2)
- November 2019 (3)
- October 2019 (1)
- September 2019 (2)
- August 2019 (3)
GitKraken is on a mission to make Git easier, safer and more powerful across multiple surfaces and environments that development teams use.
Over 10 million developers from more than 100,000 organizations worldwide rely on GitKraken to get their work done. Since 2014, we've been rapidly developing the legendary cross-platform tools while reimagining an intuitive, visual approach to Git. Our team is dedicated to making tools that help software developers be more productive using Git, it's truly our passion. We develop software that's in use by the world's most elite companies like Apple, Google, Microsoft, Amazon, and thousands of other leading organizations.
We Make Git Tools Devs Love.