Claude Code Adds a GitLab Merge Request Badge to the Footer

Claude CodeAug 17, 2026View original changelog

Claude Code now surfaces a live GitLab merge request badge in the footer and statusline, mirroring the GitHub pull-request badge that already existed. Developers on a GitLab remote with an authenticated glab CLI see the MR number (!N) along with its current state — draft, pending, or green — without leaving the terminal. The change closes a long-standing gap for teams whose primary git host is GitLab rather than GitHub.

Key Takeaways

GitLab now has feature parity with GitHub for merge request status visibility directly in Claude Code's footer and statusline.
The badge shows the merge request number in GitLab's native !N format, distinguishing it from GitHub's #N pull request numbering.
Three states are surfaced at a glance: draft, pending, and green (approved/passing), matching the existing GitHub PR badge behavior.
Activation requires no new Claude Code configuration, just a GitLab remote and an authenticated glab CLI already present on the machine.
The feature extends a broader pattern of GitLab investment in Claude Code, following earlier additions like GitLab-aware plugin marketplaces and glab credential redaction.
It reduces context-switching to a browser for teams whose review workflow lives entirely on GitLab rather than GitHub.

GitLab Gets Feature Parity With GitHub

For most of its life, Claude Code's footer and statusline badges have been a GitHub-first feature: open a pull request against a GitHub remote and a small status indicator appeared showing whether the PR was still a draft, pending review, or green and mergeable. Teams working against GitLab had no equivalent, even though Claude Code has steadily added GitLab-specific tooling elsewhere (credential redaction for glab tokens, GitLab-aware plugin marketplaces, and MR support in --worktree and the agents view).

Version 2.1.234 closes that specific gap. Repositories with a GitLab remote and an authenticated glab CLI now show a merge request badge in the same footer and statusline location the GitHub badge occupies, formatted as !N to match GitLab's own merge request numbering convention. The badge reflects the same three states as its GitHub counterpart: draft, pending, and green (approved/passing).

Why It Matters

For teams standardized on GitLab, this removes one more reason to tab out to a browser mid-session. A developer iterating on a change inside Claude Code can now glance at the statusline to confirm a merge request's pipeline and review status has gone green, the same way GitHub-hosted teams already could.

Setup

The badge activates automatically once two conditions are met: the repository's git remote points at a GitLab host, and the glab CLI is installed and authenticated on the machine. No additional configuration is required inside Claude Code itself.