## Problem glab CLI MR [gitlab-org/cli!3240](https://gitlab.com/gitlab-org/cli/-/merge_requests/3240) adds a `Coding-Agent/{name}` token to glab's User-Agent header when a coding agent (Claude Code, Codex CLI, Cursor, OpenCode, or any agent setting `AI_AGENT`) is detected. The full header looks like: ``` glab/v1.97.0 (darwin, arm64) Coding-Agent/claude-code ``` The server side doesn't read this token yet. The existing Rails regex (`^glab/v`) only matches the version prefix and ignores everything after it. Right now nobody reads it. ## Proposed solution Parse the `Coding-Agent/{name}` suffix from the User-Agent on API requests already identified as glab traffic. Expose the agent name as a property on the existing `i_code_review_user_gitlab_cli_api_request` event (or a new event), so we can measure what fraction of CLI API traffic comes from coding agents and which agents are most common. The canonical agent name values are: `claude-code`, `codex`, `cursor`, `opencode`, or any freeform string matching `[A-Za-z0-9._-]+` (from the `AI_AGENT` env var). Absent token means human or unidentified.