GitLens

"MCP is described as USB for AI."

- Eric Amodio CTO @Gitkraken & Creator of @gitlens.bsky.social

Watch GitKon LIVE: gitkon.wistia.com/live/events/...

Save the date: GitKon 2025 is December 10-11.

Two days. Virtual. Free. Built for developers who care about craft over hype.

10K+ builders. Real code. Actionable workflows.

Plus, the chance to win $2500 for the GitKon Game Jam.

Secure your spot today: gitkon.com?1?source=org...

#GitKon

GitLens hit a milestone that shows what happens when you solve real problems for developers.

We started with a simple idea: make Git history visual, intuitive, and actually useful inside VS Code. Eight years later, developers have spoken.

Thanks for trusting us with your Git workflow. 🙌

54%+ of developers now code with Git inside their editor. GitLens brings inline blame, file history, and powerful visualizations directly into VS Code. No context switching. Just flow.

GitLens Release Notes Find out what’s new, what’s fixed, or just take a trip down memory lane remembering those bugs of yesterday.

Live today in GitLens 17.5 (included with GitKraken Pro).

Full release notes: help.gitkraken.com/gitlens/gitl...

What Git task would you trust your AI with if it actually understood your repo?

Ask your AI: "Help debug this merge conflict"

MCP → reads branch history, explains the conflict in plain English, suggests safe resolution.

This is what it looks like when your AI finally understands Git.

Ask your AI: "Start work on JIRA-123"

MCP → creates a feature branch using your team's actual conventions.

No copy-paste. No guessing.

Ask Copilot: "Who changed this function and why?"

GitKraken MCP → pulls real commit history from GitLens.

No hallucinations. Just Git facts.

GitKraken MCP gives agents a single conversational layer to run Git workflows confidently.

One integration → your AI becomes Git-aware across GitHub, GitLab, Bitbucket, and Azure DevOps.

Right inside VS Code, Cursor, Windsurf, and Kiro.

Without MCP, your AI is guessing.
It doesn't know:

Who changed this function
Why a merge conflict exists
What branch naming rules your team uses

Result? Hallucinated commit messages and unsafe suggestions.

Your AI assistant doesn't actually understand Git.
It can't manage history, branches, commits, or PRs reliably.

GitLens 17.5 changes that with GitKraken MCP.

Here's what that means for your workflow 🧵

GitLens wasn’t born in a boardroom.

It started as a late-night side project to solve one dev’s biggest Git pain.

Now? It’s one of the most popular VS Code extensions ever.

Hear GitLens creator Eric Amodio tell the origin story
🎥https://youtu.be/B-nYz80puwU

GitLens Release Notes Find out what’s new, what’s fixed, or just take a trip down memory lane remembering those bugs of yesterday.

Want to know more details about GitLens 16.1? Check out the full release notes below 👇

help.gitkraken.com/gitlens/gitl...

GitLens is smarter with AI. With support for the latest Gemini AI models in GitLens, you can generate commit messages, explain changes, and do more—faster and more intuitively.

Avoid merge headaches with GitLens Proactive Conflict Detection (PRO). Get clear warnings about potential conflicts right in the Home View—and during rebases or merges—so you can resolve conflicts before merging.

Merge Target Status (PRO) makes it easy to track branch status in relation to merge targets. You can now quickly see if branches are ahead, behind, or up-to-date with their merge targets and eaily initiate a rebase or merge to keep them in sync.

The Launchpad now supports expanded PR search. Find any pull request, not just the ones tied to you, for better visibility and control.

"Start Work" just got an upgrade - Create branches from issues with a streamlined workflow. Plus, GitLens now connects issues to branches to track everything in the Home View and Commit Graph. GitLab Issues users: you can now Start Work on your issues too!

The Home View now features redesigned branch cards that display branch status and branch owners, as well as associated work items and pull requests—everything you need at a glance.

GitLens 16.1 Release Notes

🚀 GitLens 16.1 is here! Bringing powerful new enhancements like Merge Target Status, Proactive Conflict Detection and Gemini model support to supercharge your developer workflow.

Here's a 🧵 on what's new in this release:

GitLens — Git supercharged - Visual Studio Marketplace Extension for Visual Studio Code - Supercharge Git within VS Code — Visualize code authorship at a glance via Git blame annotations and CodeLens, seamlessly navigate and explore Git repositories, gain...

💡 Try GitLens 16 Today

If you’re already using GitLens, update to version 16.

New to GitLens? Install it here:
bit.ly/40LgHW5

Learn more in the release notes:
bit.ly/3CvVvsY

Get started with GitLens:
bit.ly/3ObJsDN

New Commit Graph Filtering 🔍

Zero in on what matters with new filtering tools. Quickly find changes without the noise.

Introducing "Start Work" ⚡

Start tasks faster—create branches or link issues directly from the command. Pro users can integrate with tools like Jira for an even smoother experience.

GitLens 16 New Home View

Reimagined Home View 🏠

The reimagined Home View is your project dashboard, helping you track tasks, recent changes, and progress. Stay organized with a clear view of repos, branches, and tasks.

Feedback welcome! Details here: bit.ly/3Z5SwjN

Consolidated Source Control View 🗂️

All your GitLens views (Commits, Branches, and more) are now in one place for better organization. Need flexibility? Detach views as needed.

GitLens 16 Release Summary

GitLens 16 is here, bringing big improvements to Git workflows in VS Code. The new, enhanced Source Control View makes it easier than ever to stay on top of your repos, branches, and commits—all in one place. Here’s what else is new 🧵👇

#Git #GitLens #VSCode #ReleaseNotes #AI #VSCodeExtensions