# GitLab Introduces AI Governance Dashboard for Agent Visibility Centralized tracking for internal and external AI coding agents to mitigate shadow AI risks. - **Source:** [GitLab](https://brifing.si/source/76101668-80db-4240-8676-e968d2b72546) - **Published:** 2026-10-20 - **Topic:** [Software & Engineering](https://brifing.si/c/engineering) - **Original article:** - **On Brifing:** https://brifing.si/s/30850f14-550a-4efd-b92d-900ea2f6197f ## Addressing Shadow AI Risks The proliferation of AI coding agents like Claude Code, Cursor, and Codex creates significant visibility gaps for organizations. Developers often run these tools locally, leading to shadow AI activity that remains untracked. GitLab's new dashboard addresses this by centralizing activity data, ensuring that every agent interaction is recorded and linked to specific developers. ## Unified Agent Monitoring The AI Governance Dashboard consolidates data from both the internal GitLab Duo Agent Platform and externally connected agents. By providing a single view, it allows security teams to identify which agents are running, who initiated them, and which projects were modified. This eliminates the need to manually stitch together disparate data sources for audits. ## Quantifying Agent Activity Trends Three primary tiles at the top of the dashboard provide a baseline of agent performance over seven or thirty-day periods. These metrics track the number of agents, total sessions, and tool calls made. Daily trend analysis helps teams spot anomalies, such as sudden spikes in tool usage that might indicate unauthorized software adoption. ## Detailed Audit Trail Capabilities Traditional audit logs were designed for human actions, often failing to capture the complexity of AI-driven code changes. GitLab now records every agent action as an audit event, including the specific model used, tools called, and MCP servers involved. This provides an immutable record essential for incident investigation and regulatory compliance reporting. ## Streamlining Compliance and Evidence When auditors request proof of AI usage, teams can now download session evidence directly from the dashboard. For advanced security needs, organizations can stream these events into their existing security information and event management (SIEM) systems. This capability ensures that accountability is maintained even as development teams rapidly adopt new AI coding tools. ## Configuration and Access Requirements To utilize the dashboard, users must hold an Owner role or a custom role with read_agent_artifacts permissions at the top-level group. AI audit event storage is disabled by default and must be manually enabled within the Data and privacy settings. This ensures that organizations maintain strict control over their internal data collection processes. ## Integrating External AI Agents Connecting external agents requires the GitLab CLI version 1.122.0 or later on macOS or Linux. Running the command 'glab govern setup' installs necessary hooks for Claude Code, while additional flags capture Cursor and Codex sessions. A background job transmits these sessions every 30 minutes, ensuring the dashboard remains updated with current developer activity. ## Strategic Importance of Governance As AI-assisted coding becomes standard, the ability to govern these tools is as critical as the code itself. By providing transparency into agent behavior, GitLab enables organizations to balance developer velocity with necessary security oversight. This beta release marks a shift toward proactive AI risk management within the software development lifecycle. ## Sources covering this story - https://about.gitlab.com/blog/ai-governance-dashboard/ — --- _Summary written by Brifing from the original reporting. Copyright in the original article belongs to its publisher; read the full piece at the link above._