Follow Discord
Sweep 12 Nov 2026 · 23:00Z Build v2.1.323 540 read Stable v2.1.311 Latest v2.1.323 Next v2.1.323 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.323entry #73

Claude Code v2.1.323 ·

A GitLab merge request badge that uses the glab tool

A new badge for GitLab merge requests runs the glab command-line tool in your session's folder, with safety checks first

You'll notice New Features
JSON All of v2.1.323
You'll noticeTier: how much it should matter to you
4Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
GitLabArea: what it touches
New FeaturesKind: in v2.1.323,
What probably matters to youSection of the release

Unclear The default of the switch that controls the badge is not known, so it is unclear whether the badge appears.

What

Claude Code has a new badge for GitLab merge requests. A merge request is GitLab's name for a proposed code change. To fill the badge, Claude Code looks for the glab command-line tool and runs it in the session's folder. It does not run glab when:

  • a local glab configuration is found
  • the folder is an outside checkout
  • it cannot work out which folder to run glab in

The badge sits behind a remote switch.

Why

If you use GitLab, you may see a badge for your merge request.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe default of the switch that controls the badge is not known, so it is unclear whether the badge appears.

See this entry in the whole of v2.1.323 →

Feedback