Claude Code adds GitLab support. Agents stop assuming GitHub.

Every AI coding agent shipped in the last two years assumed your code lives on GitHub. Not stated anywhere — just baked into the URL parsers, the plugin installers, and the setup tips. Two Claude Code releases this week quietly fixed that, and GitLab support is now first-class across worktrees, marketplaces, and secret handling. If you run a self-hosted GitLab because a client or a compliance requirement said so, this is the first week the tooling stopped treating you as an edge case.

What actually happened

From Anthropic's changelog, version 2.1.232 added GitLab support to plugin marketplaces — bare gitlab.com repo URLs, including nested subgroups, now clone the way github.com URLs do, and clone auth-failure hints name your actual git host instead of guessing GitHub. It also added secret redaction for the full GitLab token family (glrt-, gloas-, glptt-, glagent-, glimt-, glsoat-, glcbt-, glft-, glffct-), with full redaction of routable glpat- and gldt- tokens. The glab CLI config store now gets the same sandbox and credential-path protection that gh already had.

Version 2.1.233, the next day, added GitLab merge request URL support to the --worktree flag and the claude agents view, where MRs render as !N — GitLab's own notation, not a GitHub #N translated badly. It also stopped the GitHub app setup tip from appearing in repositories whose origin remote is on gitlab.com or bitbucket.org, and widened the enterprise marketplace tip to cover internal git hosts generally.

Why GitLab support matters for your business

Nested subgroups is the tell. Nobody adds subgroup parsing for a hobby project. That is what a self-hosted GitLab looks like at a company with an org chart, and it means agent tooling is being built for teams that never migrated to GitHub and are not going to.

For small teams, the practical unlock is the credential handling, not the merge request links. An agent that can clone from your host but does not know its token prefixes will happily print one into a transcript. Redaction covering nine token families plus glab config protection is the difference between "we could try agents on our repos" and "we can try agents on our repos without a policy conversation."

The broader read: assume the GitHub-first period of AI dev tooling is ending, and stop treating platform migration as a prerequisite for using agents. We build on client infrastructure regularly — self-hosted GitLab, Bitbucket, plain SSH remotes — and the honest answer for the last year was that tooling support was uneven. That answer is changing. Check your own stack's agent support again if you wrote it off six months ago; the ground moved.

Sources: Claude Code CHANGELOG (Anthropic).