Paste into Claude Code / CLAUDE.md task

# DevAgentRadar → Claude Code

You are helping me adopt a real coding-assistant change. Work only from the facts below. Do not invent features.

## Context
Assistant: Claude Code
Proposal: Surface live GitLab MR badges in Claude Code footer and statusline
Summary: On Claude Code v2.1.234, authenticate glab and use GitLab remotes so the new footer/statusline badge shows MR !N with draft/pending/green states during coding sessions.
Primary source: https://github.com/anthropics/claude-code/releases/tag/v2.1.234

## Why it matters
v2.1.234 adds a GitLab merge request badge to the footer and statusline when a repo has a GitLab remote and an authenticated glab CLI. That puts draft/pending/green MR state next to the session and reduces browser context switches. The same release also fixed repository detection mis-reading git remote hosts with unusual userinfo, which previously produced wrong-host links and repo-specific behavior—so cleaning remotes and standardizing glab auth makes the badge reliable across the team.

## Suggested actions
1. Upgrade Claude Code to v2.1.234 on every machine that should show MR status
2. Install and authenticate the GitLab CLI for your host, e.g. `glab auth login --hostname gitlab.com` (or your self-managed hostname)
3. In each active repo, ensure the origin remote is the real GitLab host: `git remote -v` and fix SCP-style/userinfo URLs that point at the wrong host
4. Open the repo in Claude Code on a branch with an open MR and confirm the footer and statusline show `MR !N` with draft, pending, or green state
5. Document for the team: badge requires a GitLab remote + authenticated glab; no badge means re-check `glab auth status` and `git remote -v`

## Config surfaces this release may change
- agent context files **(high confidence)** — check your repo before applying
- permission rules **(high confidence)** — check your repo before applying
- background and headless runs **(high confidence)** — check your repo before applying
- settings files — check your repo before applying
- MCP servers — check your repo before applying
- skills — check your repo before applying


## Your job
1. Restate the change in one sentence.
2. Propose a minimal plan for my repo (or a throwaway pilot).
3. Implement only what I approve; prefer small diffs and tests.
4. Call out risks (permissions, breaking APIs, cost).

Start by confirming you understood the proposal.