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. It shows MR !N with draft, pending, or green states only when the repo has a GitLab remote and glab is authenticated. If origin is not GitLab or glab is logged out, the new surface stays blank and you still leave the session to check MR identity and pipeline/review state. Point remotes at GitLab and complete glab login so coding sessions actually display the live MR.

Suggested actions

1. In this repo run: git remote -v && glab auth status. If no remote host is GitLab, set one (e.g. git remote set-url origin <gitlab-clone-url> or git remote add gitlab <gitlab-clone-url>). If glab is not logged in for that host, run glab auth login and finish GitLab auth. Then restart Claude Code v2.1.234.
2. After glab auth, run glab mr list. If there is no MR for this branch, create one with glab mr create. Reopen Claude Code v2.1.234 in this repo and confirm footer and statusline show MR !N with draft, pending, or green matching that MR.
3. Paste to an agent: On Claude Code v2.1.234, do not file a missing MR badge bug until both gates pass: git remote -v includes a GitLab host, and glab auth status reports a logged-in account for that host. The MR !N draft/pending/green badge is not a /config toggle; it appears only with GitLab remote plus authenticated glab.
4. Keep glab authenticated in every GitLab workspace you open with Claude Code (glab auth status must succeed). Do not retarget origin to GitHub or a non-GitLab mirror if you want the live MR !N badge in the footer and statusline.

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

After you finish

Do not report this as applied to DevAgentRadar. You cannot write the visitor's loop.

Tell the human: open https://devagentradar.com/proposals/claude-code-v2-1-234-surface-live-gitlab-mr-badges-in-claude-code-footer and mark Applied, Skipped, or Failed. Proposal id: c213d728-c7e0-45db-95de-a76caa762362

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.